Cruise Control .NET is used for triggering the build when anything changes in the trunk and it also gives you a nice web dashboard with information about the builds. The Cruise Control Tray application is also good enough for instant status about the build process.
For a very nice tutorial about implementing continuous integration with MSBuild scripts and Cruise Control .NET, see this blog post by Carel Lotz from the South African .NET Developer Portal.
Visit the MSBuild Community Tasks Project for a lot of useful MSBuild tasks to include in script.
Hopefully this will increase the speed of Code Style Enforcer releases, which unfortunately has been rather low lately. I have made a small update though, which solves the bug in DXCore 2.2.2, described here.
So for all of those who are using the latest DXCore version, stay put, since there will be a new release this weekend!
I have reported this to DevExpress and they will have it fixed for their next release. I am now trying to get an answer to when this will be. Until then and if possible use DXCore 2.1.3, which I know will work, or bare with me until the next DXCore version is released.
Read more about the issue here "http://community.devexpress.com/forums/ ... 84403.aspx".
First of all it clearly documents the reason for violating the code rule, and thus avoids the problem of someone "correcting" it. It also makes the redline disappear from under the rule violation, since the attribute clearly specifies for Code Style Enforcer that it is a deliberate violation.
I will now give you an example of where and when we use it in our project. We demand that all interfaces should be explicitly implemented and for each thus method/property, there should be a matching method/property in the class marked as protected virtual. This makes it possible to override the implementation in derived classes and it also makes it easier and more direct to call local method/properties without the need to first cast yourself to that interface.
But sometimes the protected method/property must be public due to serialization or data binding and when we make it public it violates the explicit interface implementation rule. Therefore it is very nice to be able to clearly specify that we want/need to violate this rule, but it is deliberate, and we can specify why we did so.
In order to use the attribute you must add a reference to the CodeStyleEnforcer.Attributes assembly, which can be found in the normal Visual Studio reference list. Then simply add the CSEIngnoreRule attribute to the member that violates a rule and specify the rule type it is deliberately violating, i.e. Name, Visibility or Implementation. Make sure to also specify a reason for violating the rule.
Another very nice thing with the CSEIgnoreRule attribute is that it only exists in design time in Visual Studio. It never gets compiled into code and thus does not exist in the production code.
• An easier and more user friendly way to choose between local or global, i.e. shared, rules for a solution.
• Name rules and perhaps also visibility rules must be more flexible, e.g. be able to have different name rules depending on the visibility of a language element. I hope I can make it flexible enough without the need for regular expressions, since I abandoned that path in order to add the auto correction feature.
• Hungarian notation is also something that would be nice to support again, without regular expressions.
If you have any more comments or suggestions, please let me know.
Now you have heard my thoughts about the next version, but of course this can all change, we are living in an agile world after all!
I also added activation/deactivation of Code Style Enforcer to the context menu of the Visual Studio solution.
An uninstall of any previous versions has to be made from the Add/Remove Programs dialog, before installing the new beta version. Why? Well, it has to do with Custom Actions and Upgrade Installations, read my previous blog post for more thorough information.