Code Style Enforcer 3.5 is now here, and better than ever. A reworked and more flexible rule system is now in place, where it is possible to override rules for specific code types based on modifiers and visibility. For example, we might want some specific name rule for parameters marked as ref or out, or we require public visibility on static methods, but any visibility on instance methods.
A new default name rule override has been added to the standard rules, namely that methods marked with the async keyword must have “Async” as suffix.
Please give this new version a try and let me know if there are any issues with this new rule system, or any other issues for that matter.
Be sure to use DXCore 11.2.7 or later, since the new rule system is dependent on this release.
New Features
• A redesigned and more flexible rule system supporting more granular name and visiblity rules based on not only the code type, but also on modifiers and visibility.
• The separate rule configurator application has been removed and both local and global rule configurations can now be made within Visual Studio instead (Tools menu --> Code Style Enforcer). This also solves the problem where the configurator application stopped working for each new release of DXCore.
Bug Fixes
• Code rules can now be saved upon change even if rule files have become readonly, e.g. by using TFS in offline mode.
Breaking Changes
• Due to changes in the code rule definitions, any old customized code rules will get backed up and the new default rules will instead be loaded, when opening the Global Code Rules Options dialog in Visual Studio or a previously Code Style Enforcer activated solution.
Download Code Style Enforcer 3.5.17

Download Code Style Enforcer 3.0.72

Download Code Style Enforcer 3.0.71

Download Code Style Enforcer 3.0.51

Download Code Style Enforcer 3.0.43

Next