Tuesday, January 29, 2008, 07:33 AM - Code Style EnforcerUnfortunately I’ve ran into some problems with my optimization plans and DXCore 3.0+ as well. I’m really satisfied with my optimization code for Code Style Enforcer, but unfortunately DXCore doesn’t work very well with background thread analysis, resulting deadlock related situations.
I was then informed by DevExpress that the new DXCore 3.0+ version was supposed to have special support for background thread analysis through the new code issue provider model. This, on the other hand, proved to be too much beta still since it didn’t behave as expected.
Right now I’m waiting for the DevExpress support team to analysis my code and the threading issues with DXCore 2.5+. The other alternative is to wait for a newer and more final version of DXCore 3.0+ and hopefully the background thread analysis will be good enough there, even though I’m rather skeptical about it right now.
The optimization release is therefore put on hold for now, so I might look into some other issues first. Right now I feel in need of a good vacation though and therefore I’m leaving for Florida on Friday. I can only hope that I’ll get back with a lot of new enthusiasm :)!!!
Sunday, January 6, 2008, 04:36 PM - Code Style EnforcerDXCore version 3 is now available for download, but currently version 2 is the only supported version by Code Style Enforcer. The next release of CSE will be a performance upgrade, where optimizations have been made to the code rules checking engine, i.e. read previous log post.
After that I will begin targeting Code Style Enforcer against the new version 3 of DXCore, in order to use some new nice features of that release. This means that DXCore version 3 will soon be a requirement instead of version 2.
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, 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.