For me, StyleCop is a valuable element in the C# toolchain. It helps to maintain a consistent coding style within a given context, be it a single file, project, solution, a dev team, an entire organisation or, potentially, even the entire C# industry.
Until now, StyleCop has been made available principally as a Visual Studio add-in which can be invoked on demand by a developer - see the documentation for more details.
It is also possible to run StyleCop as part of the build process - see ‘Setting Up StyleCop MSBuild Integration’. As the documentation shows, it is even possible to add the StyleCop binaries to a source code repository and have the analysis run whenever and wherever the assemblies are built. The advantage of this approach is that StyleCop does not need to be installed on every machine where the assemblies are built and is therefore guaranteed to run during every build.
To set this up, a number of manual steps are involved:-
- Install the add-in, choosing the option to install MSBuild files (or grab the binaries and targets from elsewhere)
- Copy the StyleCop binaries and targets files into your source code repository
- Add <Import> elements to your csproj files pointing to the StyleCop targets file
(There are variations on this theme such adding an environment variable pointing to the targets file to make csproj file maintenance easier.)
As I’m sure the astute reader is already asking, wouldn’t it be good if all this were automated?
StyleCop.MSBuild is a Nuget package which automates this process. In order to add MSBuild-integrated StyleCop analysis to your projects, simply install the StyleCop.MSBuild Nuget package in the normal way using either the Package manager console or GUI. The installation script will take care of adding the relevant
StyleCop.MSBuild installs exactly the same binaries as those contained in the official StyleCop release. Whenever a new version of StyleCop becomes available, a new version of StyleCop.MSBuild will be released alongside with a corresponding version number. To update to the new version, simply update your Nuget packages in the usual way and the StyleCop.MSBuild installation script will take care of updating the
(Note that the ‘StyleCop.MSBuild’ Nuget package is not to be confused with the ‘StyleCop’ Nuget package, which is intended for referencing as a library for writing custom StyleCop rules.)
##For current users of versions 18.104.22.168 or 22.214.171.124
If you are already using StyleCop.MSBuild version 126.96.36.199 or 188.8.131.52 then updating to 184.108.40.206 or higher will not work. Those versions simply added the binaries to your source code repository and did not affect your projects in any way which means that Nuget doesn’t recognise them as being installed in any projects, only the solution. Instead of updating from either of these versions, remove them and then install version 220.127.116.11 or higher.
Thanks to eddie_butt @ codeplex and Amy Dullard @ Microsoft for suggesting the addition of the auto-import feature. Thanks to Andy Reeves @ StyleCop for offering to pull the package code into the main project (when either I or someone else get round to providing a patch!).
The source code for this package is currently hosted at https://bitbucket.org/adamralph/stylecop-msbuild. Pull requests are gladly accepted.
It is planned that this will be merged into the main StyleCop project at CodePlex at some point in the future.Disqus