• 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
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!
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.
This workes perfectly fine when building it inside Visual Studio 2010, but when building it from the command line using MSBuild 4.0 it fails, complaining about not finding the GetDeviceFrameworkPath in the Microsoft.CompactFramework.Build.Tasks. This has to do with an error in the configuration file for MSBuild.
The solution is to edit the msbuild.exe.config file in the [Windows]\Microsoft.NET\Framework\v4.0.21006 folder and to remove the binding redirect for Microsoft.CompactFramework.Build.Tasks to version 10.0.0.0, which does not exist yet.
Lines to remove:
<assemblyIdentity name="Microsoft.CompactFramework.Build.Tasks" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-22.214.171.124" newVersion="10.0.0.0"/>
I know that I had configured the apartment state to STA in the NUnit config file corresponding to the NUnit project file (or assembly). TestDriven.NET states that it defaults to run with STA as apartment state, but still it complained about not being STA.
The solution for me was to explicitly add the RequiresSTA attribute to the class being tested. The RequiresSTA attribute can be added to individual test methods, an entire test fixture or the whole assembly.