Monday, December 31, 2007, 11:55 AM - Code Style EnforcerWhat’s going on with Code Style Enforcer, you might ask?! Well, lately I’ve been investigating performance issues related to CSE. In my team at work, some team members have been experiencing lag in Visual Studio when typing or scrolling in the code editor. It turned out that it had to do with CSE, since I do the code rule violations check on the DXCore Paint event, which occurs quite often. The lag most often occurs for big solutions and/or having a lot of event handlers.
I’ve now redesigned when and how the code rule violations are checked, by utilizing the DXCore Parse event together with asynchronous calls. I’m almost done with the optimization and hopefully we can try it out in our team in the upcoming week.
A new release can therefore be expected in early January, which will perform a lot better, but unfortunately won’t have a lot of new features, if any at all.
Happy New Year!!!
Friday, November 2, 2007, 03:57 PM - Code Style EnforcerI noticed a strange behavior today, in Visual Studio 2008. When I load a solution, the rules for Code Style Enforcer doesn't seem to be loaded. If I close the solution and open it up again, it is however, so nothing seems to happen the first time.
I'm not sure if this has something to do with Visual Studio 2008, DXCore 2.5.8, Code Style Enforcer 2.1.32 or if it only happens to me.
Please comment on this blog post if any of you experience the same problem and in which environment. I will look more into it when I get back from DevConnections.
Thursday, November 1, 2007, 06:17 PM - GeneralIt's time for DevConnections, Las Vegas, in the next week, chaired by Juval Löwy and Carl Franklin. Juval Löwy, from IDesign, is the man behind the C# code standard used by Code Style Enforcer, as default rules.
I'm really looking forward to this conference and to Las Vegas of course. We are about eight people from here, coming from different companies, who are attending the conference. We're leaving this Saturday and will stay for a little over a week, so hopefullt we'll experience more than just the conference, e.g. Las Vegas night life, Grand Canyon, etc.
So if any of you are going there, we might bump in to each other :)!
Thursday, November 1, 2007, 05:53 PM - Code Style EnforcerFirst of all I'd like to thank you all for using, or at least trying out, Code Style Enforcer. I've had over 2000 unique downloads of the latest 2.1.29 version.
Now Code Style Enforcer 2.1.32 is here with one main feature in focus, due to user requests, and that is report generation. It's now possible to generate code rule violation reports for a solution, with different templates. Report data is stored as XML and XSLT is used to transform the data into different reports. The XSL templates included are a detailed violations report for every code file in a solution and a summary report showing the total number of violations of a specific kind, i.e. name, visibility, implementation. It's also possible to add custom report templates by simply adding them to the ReportTemplates directory.
Report generation can be accessed through the context menu of the solution, where it's also possible to activate/deactive Code Style Enforcer.
DXCore 2.5.8 is now required for this version of Code Style Enforcer. Uninstall any previous versions of Code Style Enforcer and DXCore, before installing the new versions.
Thursday, October 11, 2007, 08:53 PM - Code Style EnforcerIt’s been quite some time now, since I last posted some information about what’s going on. Well, to tell you the truth, I’ve been rather busy lately, changing employer among other things. So, unfortunately I’ve not been having that much time with Code Style Enforcer, but hopefully that will change.
The earlier posted information about a new version with a more detailed configuration of the code rules, e.g. different name rules depending on visibility or keyword, will have to wait a little longer, due to some architectural decisions.
A new version is planned to be released real soon though, containing a new feature where it’s possible to generate a report, i.e. XML file, containing information about all code rule violations for all files in a solution. Some users have wished for a feature like this, so I thought it would be a good thing to implement. That‘s what’s being agile after all.
A fix with the MSI installation of Code Style Enforcer for Windows Vista x64 is also planned for this release. I think you can expect this new release within a week or two…