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 Blog by Joel Fjordén a.k.a. Will o Wisp
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 ( 5 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 ( 5 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 ( 143 views )   |  related link

Server HD Crash! 
Thursday, July 19, 2007, 06:17 PM - Code Style Enforcer
Yesterday our Build/SVN/CI Server gave up, the HD suddenly sounded like THUMP THUMP DDRR GRR THUMP THUMP, yeah you know the drill...

Where are all backups when you need them, well I will try to get all data back and have the server up and running again as soon as possible, but it will have to wait until I'm back from my two weeks of vacation in USA. Unfortunately this means that the version to be released this week will also be delayed until then...

I´ll let you all know as soon as everything is back to normal, until then enjoy the summer, cause I certainly will!
1 comment ( 5 views )   |  related link

More Rules to Come 
Sunday, July 15, 2007, 12:54 PM - Code Style Enforcer
Right now I’m working on extending the code rule architecture, making it possible to add name rules to more code types. The upcoming version, which probably will be released the next week, will first of all include new name rules for enumerations, enumeration values, exceptions, attributes and delegates. It will also be possible to specify different visibility rules for those. Suffix has also been added for each name rule, in the same way prefix works.

Besides from more rules for new code types, it will be possible to combine code types with visibility and keyword. Different name rules for public fields and private fields, for example, are therefore supported. The keywords, e.g. static, abstract, virtual and sealed makes it possible to add different name rules for static classes and instance classes, or different visibility rules for that matter. This will of course take some more time to implement, but the work has already begun. My guess is that it will be released sometime in week 33, since I’m now on vacation and will be going to New York for two weeks.

I hope you’ll like this extra granularity when it comes to rules, since a lot of you have requested it.

33 comments ( 42710 views )   |  related link

Back Next