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 3.0.17 Beta for Visual Studio 2010
Code Style Enforcer 3.0.17 Beta for Visual Studio 2010 
Wednesday, September 1, 2010, 03:40 PM - Code Style Enforcer
Since I'm now back at work, since a couple of weeks, after a very relaxing vacation, I've also managed to get the time to add some missing, and improved, features to Code Style Enforcer for Visual Studio 2010.

Code Style Enforcer 3.0.17 Beta

New Features

• Activation/Deactivation of Code Style Enforcer can now be done for the complete solution and for specific projects. The "Active" command is available from the context menu when right-clicking on the solution node or a project node in the Solution Explorer.

• Generate reports functionality added for generating an XML file containing all rule violations for the complete solution. Different XSL style sheets can then be used for a proper presentation of the data. The "Generate Report..." command is available from the context menu when right-clicking on the solution node in the Solution Explorer.

Bug Fixes

• Code Style Enforcer Configurator could crash when trying to save rules to a read-only location.

• The wrong violation description was presented for name rules where no prefix was allowed.

Known Issues (some missing features from the previous releases)

• No user interface for changing the code rules inside Visual Studio, but it can still be done using the Code Style Enforcer Configurator application or manually by editing the XML rule files.

Download Code Style Enforcer 3.0.17 Beta
3 comments ( 41 views )   |  related link

New Beta Release of Code Style Enforcer for Visual Studio 2010 
Friday, July 23, 2010, 07:28 AM - Code Style Enforcer
Code Style Enforcer 3.0.13 Beta

New Features

• New improved activation dialog in WPF.

• Tooltips added with descriptions of the code rule violations (presented when hovering over a violation).

• Smarttags added for correcting name and visibility rule violations (activated by putting the cursor on a violation).

Known Issues (some missing features from the previous releases)

• Same as for 3.0.7 Beta, except for the automatic correction of violations which is now available through smarttags.

Download Code Style Enforcer 3.0.13 Beta
1 comment ( 8 views )   |  related link

Upcoming Features in Code Style Enforcer 2010  
Friday, July 2, 2010, 11:11 AM - Code Style Enforcer
The features I'm working on right now, for the next beta version, are a quick info tooltip describing the reason for a violation and a smart tag for correcting code rule violations.

I will also look into getting the context menu items for activate/deactivate on projects and solution level and the possibility to generate violation reports.

Adding Code Style Enforcer to the Visual Studio option pages is of course something that also must be addressed in order to be able to configure the rules from within Visual Studio.

Let's see how many of these that will make it into the next release.
1 comment ( 8 views )   |  related link

Code Style Enforcer for Visual Studio 2010 Released 
Sunday, June 27, 2010, 08:59 AM - Code Style Enforcer
Code Style Enforcer is currently being rewritten for Visual Studio 2010 utilizing the new editor extension capabilities. Code Style Enforcer 3.0.7 Beta is the first step towards this goal and it therefore still missing some of the core functionality from the previous releases. These features will be implemented in the upcoming releases, hopefully together with some new functionality. More and more of the functionality is rewritten using core Visual Studio 2010 integration features, but DXCore, from Developer Express, is still needed for parsing the source code.

• Simplified installation, with only a single MSI file, and support for the Visual Studio Extension Manager.

Known Issues (some missing features from the previous releases)

• No user interface for changing the code rules inside Visual Studio, but it can still be done using the Code Style Enforcer Configurator application or manually by editing the XML rule files.

• No automatic correction suggestions of code rule violations.

• No menu item for toggling the active state of Code Style Enforcer, on solution- or project-level, but it can be done manually be editing the solution or project file.

• Not possible to generate code rule violation reports.


Please let me know of any bugs or strange behaviors that you might encounter.

Code Style Enforcer 3.0+ will only work with Visual Studio 2010. For Code Style Enforcer support in Visual Studio 2005 and Visual Studio 2008 stay with version 2.2.34.

Download Code Style Enforcer 3.0.7 Beta
1 comment ( 8 views )   |  related link

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 ( 7 views )   |  related link


Back Next