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 2010 Under Development
Code Style Enforcer 2010 Under Development 
Monday, June 21, 2010, 07:01 PM - Code Style Enforcer
Since a lot of faithful users have been asking about support for Visual Studio 2010, I can now announce that I have come a good way in the development of this next version.

I'm rewriting quite a lot to utilize the new editor extension capabilities in Visual Studio 2010. The first release, will probably not be feature complete with the previous versions, but the goal is to get it out as fast as possible with the bare minimum of requirements. The future goals is then to be able to plug-in even more features which hopefully should be a lot easier.

Please let me know if you are willing to sign up as a beta tester!
1 comment ( 9 views )   |  related link

Code Style Enforcer 2.2.34 
Wednesday, March 17, 2010, 05:41 PM - Code Style Enforcer
Today I'm releasing a very minor version change of Code Style Enforcer where the only difference to 2.2.10 is that it is compiled against DXCore v2009 vol 3.3 (9.3.3). The reason for this is that a few users have experienced problems with the combination of Code Style Enforcer 2.2.10 and the latest version of DXCore.

It's been quite a long time now since anything big really happened to Code Style Enforcer, and it is simply because I have not had the time I wanted and needed for it. Now I've at least setup a continuous integration environment for it, or really exchanged CC.NET which I once used in favor for TeamCity, which seems to work really great!

The next thing that will happen with Code Style Enforcer is that I will port it to Visual Studio 2010. There is now a beta version of DXCore, v2010 vol 1.0, which has some breaking changes in it that I will need to adhere to in order for CSE to work in the new WPF editor.

After releasing a version working well with Visual Studio 2010, I will look into the new extension capabilities of the new code editor in order to see what advantages this can give to Code Style Enforcer.
4 comments ( 116 views )   |  related link

Support is Coming for DXCore 9.1.3 
Friday, April 24, 2009, 08:07 AM - Code Style Enforcer
DevExpress recently released new versions of DXCore, CodeRush & Refactor, where they have a new versioning and installation structure.

A new version of Code Style Enforcer is on the way, with support for the latest DXCore. The only difference, really, is the installation path of the CSE plug-in, so until I've fixed this you can simply copy the DX_CodeStyleEnforcer DLL from the "C:\Program Files\Code Style Enforcer" folder, to the DXCore plug-ins folder located in something like "Documents\DevExpress\IDE Tools\Community\PlugIns".
11 comments ( 265 views )   |  related link

New Version Finally Here! 
Wednesday, November 12, 2008, 08:37 PM - Code Style Enforcer
The new Code Style Enforcer version is 2.2.10.

New Features

• Settings file and default location for custom rules is changed to the user's documents folder. UAC should no longer be an issue.

• Rules are now only enforced for C# and VB projects/documents.

• Possible to activate/deactivate Code Style Enforcer for each individual project in a solution.

Bug Fixes

• Method parameters are now checked for violations again.

• Implicit and explicit cast operators no longer report invalid violations.
7 comments ( 194 views )   |  related link

New Version on its Way! 
Friday, September 26, 2008, 01:20 PM - Code Style Enforcer
It's been way to long since I released a new version of Code Style Enforcer, but now I've finally took the time to get back into the code.

A new version can be expected really soon, it will mainly contain some fixes for reported bugs, e.g. invalid violations reported for implicit and explicit cast operators, and similar things.

I'm also going to have a look at the UAC issue and change where settings and rules are stored, since now it happens below the Program Files folder, which is no good.

Stay tuned!
8 comments ( 161 views )   |  related link


Back Next