Warning: strpos(): needle is not a string or an integer in /customers/a/f/c/fjorden.se/httpd.www/joel/index.php on line 31 Warning: strpos(): needle is not a string or an integer in /customers/a/f/c/fjorden.se/httpd.www/joel/index.php on line 37 Warning: strpos(): needle is not a string or an integer in /customers/a/f/c/fjorden.se/httpd.www/joel/index.php on line 43 Warning: strpos(): needle is not a string or an integer in /customers/a/f/c/fjorden.se/httpd.www/joel/index.php on line 49 Blog by Joel Fjordén a.k.a. Will o Wisp - Code Style Enforcer 2.1.32 Released
Code Style Enforcer 2.1.32 Released 
Thursday, November 1, 2007, 05:53 PM - Code Style Enforcer
First 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.
5 comments ( 82 views )   |  related link

What's Going On?! 
Thursday, October 11, 2007, 08:53 PM - Code Style Enforcer
It’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…
3 comments ( 38 views )   |  related link

New Version 2.1.29 of Code Style Enforcer 
Wednesday, August 22, 2007, 05:28 PM - Code Style Enforcer
Here comes a new version with some minor, but yet quite inconvenient, bug fixes. Almost eight hundred unique downloads of version 2.1.25, closing in on one thousand ;)! Feels very good that so many are downloading it and at least are trying it out. Thanks!

New Features

• Code Style Enforcer activation dialog made more attractive.

• More nicer looking icons.

Bug Fixes

• Visual Studio crashed, due to a bug in DXCore, when attempting to parse a class with inheritance like: class ClassXXX : ClassXXX { }.

• Installation showed a non-informative error message, "Object reference not set to an instance of an object", when DXCore wasn't installed.
1 comment ( 8 views )   |  related link

Bug Fixes in the Next Release 
Friday, August 17, 2007, 11:17 AM - Code Style Enforcer
The upcoming version, will be released with a couple of days, and will most probably not contain any new features but instead some minor bug fixes.

Bugs Fixed:
• Workaround due to a bug in DXCore, which made Visual Studio crash when interhiting yourself, i.e. same sub class as base class.

• Installation now reports an informative message if DXCore is not installed, instead of "Object reference not set to an instance of an object".

If you know any more bugs, please let me know, and I might be able to fix them for this upcoming release.

Unfortunately I've not had enough time during my vacation to look more into the implementation of having multiple name rules for the same code type but with different visibilities or keywoards, e.g. public fields and private fields. But I don't think it will introduce to much problems for me, so I think there might be a first version out within a couple of weeks.
1 comment ( 8 views )   |  related link

Code Style Enforcer 2.1.25 Released 
Monday, July 23, 2007, 10:07 AM - Code Style Enforcer
Server is now up and running with all data restored. It went a little better than expected so here is a new version of Code Style Enforcer with some added name rules and visibility rules.

In order to get the default rule standards for the new code types, make sure to press the default button in the global "Configurator" application, for globally linked rules. For locally linked rules, press the default button in DevExpress menu --> Options --> Code Standard, for locally added rules.

New Features

• New name rules added for enumeration, enumeration value, delegate, attribute and exception.

• New visibility rules added for enumeration, delegate, attribute and exception.

Bug Fixes

• Rule files no longer opened in code editor when activating CSE.
8 comments ( 146 views )   |  related link

Back Next