Download Code Style Enforcer 3.0.51
Download Code Style Enforcer 3.0.43
There seems to be some incompatibility issue with this new version of DXCore, but a new version of Code Style Enforcer targeting DXCore 2010 vol 2.3 will be released within the next couple of days!
Right now I'm looking into a more flexible code rule system, where it should be possible to fine tune rules based on a combination of code type (field, method, etc.), visibility (public, private, etc.) and keyword (static, readonly, const, virtual, etc.).
My thought is that it should also be possible to choose the current standard, and easier, configuration of name rules, but that it also should be possible to specify custom regular expressions, probably resulting in the loss of automatic name corrections or suggestions.
The other relatively large implementation feature is to enable Code Style Enforcer to enforce the rules during MSBuild, either inside Visual Studio or through the command-line, e.g. automatic build server. Inside Visual Studio the violations will be added to the Error List tool window as either warnings or errors depending on configuration.
I think and hope these features are something you all have use for, but please let me know if anything else comes to your mind.
Code Style Enforcer 3.0.32 requires the latest version of DXCore, that is 10.1.7.
• New UI for configuring code rules, utilizing grids to get a uniform view for all different rule types while also making the configuration easier to extend for a future and more flexible rule system.
• Code rules, for a specific solution, are now configurable from within Visual Studio 2010, through Code Style Enforcer -> Properties from the solution node's context menu in the Solution Explorer.
• Code Style Enforcer Configurator converted to a WPF application using the new rule configuration pages.
• Possible to configure different interface implementation rules for properties, methods and events.
• Probable prefix, in a name rule violation, was not removed from name when automatically suggesting a new name.
• Loading the default rules did not work when the local rules were the same as the global rules, i.e. the global rules were linked into the solution.
• Due to changes in the code rule definitions, any old customized code rules will get backed up and the default rules will instead be loaded, when opening Code Style Enforcer Configurator or a previously Code Style Enforcer activated solution.
Download Code Style Enforcer 3.0.32