StyleCop Checkin Policy for Visual Studio.
Check your code for StyleCop errors/warnings before you can check-in your code into Team Foundation Server.
This CodePlex site is the sourcecode for the Visual Studio check-in policy for checking your code with StyleCop. This check-in policy could be installed by the
Visual Studio gallery
Visual Studio 2013
Visual Studio 2015
or you can download it from the
- Global StyleCop settings for whole Team Project
- Import your current StyleCop settings (if you already use StyleCop) into the check-in policy
- Export the StyleCop settings of the check-in policy
- Override the settings for specific projects with the power of merged StyleCop settings files
- Thread the Check-in violations as errors, warnings or information messages in Visual Studio
- Exclude folders to be checked
- Visual Studio 2013
- Visual Studio 2015
Set the "/p:StyleCopTreatErrorsAsWarnings=false" (without quotes) parameter in your build definition to throw an error when there is a StyleCop warning. This works if you have the NuGet
package installed. This way your build will fail so no corrupt code is checked-in. This check-in policy prevents users from checking-in bad code but it is a check-in policy so it
could be overridden. You can set this parameter in your build definition on the "Process" tab, under the "Advanced" category and then the "MSBuild Arguments" property.
The original code is from another CodePlex project called
Source Analysis Policy
. This code is altered because the original project stopped supporting new versions of Visual Studio and StyleCop. The functionality is for some parts the same but a lot is altered like support for the latest StyleCop version and the
new extension methods of Visual Studio with vsix files.