SolutionCop is tool for analysing Visual Studio solutions and projects. It covers gap between FxCop (static analysis of binaries) and StyleCop (static analysis of isolated files) and allows to analyse solution/project structure and settings.

Usage: SolutionCop.exe -s MySolution.sln [-c SolutionCop.xml] [-b TeamCity]

If no configuration file is specified then tool will look for SolutionCop.xml file next to *.sln. If config file cannot be found then default one will be created next to VS solution with all rules disabled.

• Basic
  • TargetFrameworkVersion
  • TreatWarningsAsErrors
  • SuppressWarnings
  • WarningLevel
  • FilesIncludedIntoProject
  • SameNameForAssemblyAndRootNamespaTargetFrameworkProfilece
  • SameNameForAssemblyAndRootNamespace
• NuGet
  • NuGetAutomaticPackagesRestore
  • NuGetPackagesUsage
  • ReferenceNuGetPackagesOnly
  • NuGetPackageVersions
  • SameNuGetPackageVersions
• StyleCop
  • StyleCopEnabled
  • TreatStyleCopWarningsAsErrors

NuGet.exe Install SolutionCop

or

NuGet.exe Install SolutionCop -Prerelease

depending on how brave you are

• Tool is using .NET 4.0

• Check for "Copy Local" used
• Classify project by type (e.g. production, testing) and disallow references between some groups
• Proper owner in AssemblyInfo (can it be done via FxCop?)
• Proper copyright date in AssemblyInfo (can it be done via FxCop?)

• Option to fail on missing sections instead of creating them
• Provide links to rule details in output
• Treat each rule as a separate test suite for TeamCity (not sure whether it will work better than current plain list)
• Move error messages to resources
• XSD for config