CodeStyleEnforcer 2.2.10

Code Style Enforcer 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. -------------------------- Code Style Enforcer 2.2.1 New Features • Support for Visual Studio 2008. • Optimizations of the code rule validation engine, which now utilizes background threads and incremental parsing. Bug Fixes • Rules were not always loaded when opening a solution in Visual Studio 2008. Workaround has been made since bug still exists in DXCore (http://www.devexpress.com/Support/Center/p/B19561.aspx). • Context menus in code editor and on solution item didn't show. • Name refactoring didn't work in Visual Studio 2008. • bool.TryParse(stringValue, out boolValue) no longer reports a name violation (fix in DXCore 3.0). • Steps taken to assure that the MSI installer works with UAC in Windows Vista, according to blog post at http://www.shahine.com/omar/VSTOAddinsAndVista.aspx. Known Issues • Code Style Enforcer doesn't work well when UAC is turned on in Windows Vista, but for how long can you stand it anyway :). -------------------------- Code Style Enforcer 2.1.32 New Features • Possible to generate code rule violation reports for a solution, with different templates. Report data is stored as XML and XSLT is used to transform the data into different reports. The XSL templates included are a detailed violations report for every code file in a solution and a summary report showing the total number of violations of a specific kind, i.e. name, visibility, implementation. It's also possible to add custom report templates by simply adding them to the ReportTemplates directory. Known Issues • bool.TryParse(stringValue, out boolValue) reports a name violation, due to a bug in the DXCore parser. Bug has been reported and will hopefully be fixed shortly (http://community.devexpress.com/forums/t/58963.aspx). -------------------------- Code Style Enforcer 2.1.29 New Features • Code Style Enforcer activation dialog made more attractive. • More nicer looking icons. Bug Fixes • Visual Studio crashed, due to a bug in DXCore, when attempting to parse a class with inheritance like: class ClassXXX : ClassXXX { }. • Installation showed a non-informative error message, "Object reference not set to an instance of an object", when DXCore wasn't installed. -------------------------- Code Style Enforcer 2.1.25 New Features • New name rules added for enumeration, enumeration value, delegate, attribute and exception. • New visibility rules added for enumeration, delegate, attribute and exception. Bug Fixes • Rule files no longer opened in code editor when activating CSE. -------------------------- Code Style Enforcer 2.1.22 New Features • Possible to specify a custom folder for global rules, in the Configurator application. • Activation dialog in Visual Studio extended with support for specifying global and local rules. • Selecting global rules automatically links the global rules in solution, without adding any physical files. • Activation status, i.e. active or inactive, is stored in solution. • Possible to specify a required suffix for each name rule. ------------------------------- Code Style Enforcer 2.1.11 Beta Bug Fixes • Visibility rules settings not saved when changing them in tree view. • CSE configurator application lost global rule settings for pages not visited. ------------------------------- Code Style Enforcer 2.1.10 Beta New Features in DXCore 2.2.2 • Experimental support for Visual Studio Codename "Orcas". • Improved performance of the C# parser by approximately 30%. Bug Fixes • Due to a bug introduced in the IsDefaultVisibility method of DXCore 2.2.2, Code Style Enforcer reports invalid visibility and implementation rule violations. A fix for this issue has been implemented until the next version of DXCore is released. ------------------------------ Code Style Enforcer 2.1.1 Beta New Features • Code Style Enforcer now comes with an installer to make life so much easier. Uninstall of previous versions has to be made for now, since there are a known issue with Custom Actions and installer upgrades, see one of my blog posts if interested. • The different rules are now stored as XML files locally to each Visual Studio solution and are added as solution items, in a solution folder that is hidden by default. It is possible to have different rules for different solutions, but it is also possible to share rules between solutions, by linking in the XML files from a common folder. This makes it a lot easier for rules to be source controlled and shared. A windows forms application is also installed, which makes it easy to configure the global default rules that are later copied to new solutions. • Name rules are no longer configured through regular expressions, but instead with prefix, casing and valid characters. Hungarian notation is not there yet, but will make it into future version. • Name violations can automatically be refactored to valid names, through a context menu. • Visibility violations can automatically be refactored to valid visibilities, through a context menu. • Possible to override violations, by adding an attribute "CSEIgnoreRule" to targets. Why is this a good idea? Well sometimes you simply must have a class called "UTF8", for example, even though numbers are not valid. Then it is nice to be able to add this attribute as an override, which tells Code Style Enforcer that it is a deliberate violation. The attribute also takes a string parameter where one must specify a reason for deliberately violating a rule. This makes it very easy for other project member and yourself to see and remember why the code style had to be broken in that particular case. Another scenario is when always demanding explicit interface implementations, which is not always possible when it comes to data binding or serialization. Therefore it is very nice to be able to clearly specify why a rule had to be violated. • Activation/Deactivation of Code Style Enforcer added to the solution context menu. Bug Fixes • Destructors no longer report name violations, due to ~. • Operator overloaded methods no longer report name violations. • Explicit implementations of generic interfaces no longer report name violations, corrected in DXCore. • Visibility is now also checked on classes, structures and interfaces. • Selection stopped working in editor after bringing up the context menu for fixing violations. CSE context menu is now part of standard context menu in Visual Studio.