Free SharePoint Code Analysis Tool available

Those who know me, also know that I’m passionate about SharePoint development process and code quality since many years. This passion resulted first in creation of SPSF SharePoint Software Factory together with my "old" fellow Matthias Einig, later we created SPSD SharePoint Solution Deployer and finally SPCAF SharePoint Code Analysis Framework has been added.
Therefore I'm indescribable happy and proud that after many years of work last week the final release of the free SharePoint Code Checker (SPCop) has been published by Matthias. SPCop is based on the SharePoint Code Analysis Framework and is available for free. Developers can use it directly in Visual Studio and can analyze their SharePoint code with more than 300 rules (check out the list of rules here).
We can now detect syntax errors in XML directly in Visual Studio and not only after a deployment to SharePoint. We can now easier follow best practices and can learn how to develop better SharePoint solutions. In the future also more rules for analysis of SharePoint apps wil be added and will make it easier to develop high quality SharePoint apps.

So, see for yourself:

SharePoint Code Check (SPCop) is the free code analysis component of SharePoint Code Analysis Framework (SPCAF).

SPCop is a Visual Studio Extension to analyze SharePoint code. This includes
  • SharePoint solutions (.wsp) for SharePoint 2007 / 2010 / 2013
  • SharePoint 2013 apps
SPCop cannot only analyze assemblies like other tools as FxCop or SPDisposeCheck. It can also analyze all the XML code in SharePoint packages like Features, ContentTypes, ListTemplates and all the other files like controls (.ascx), pages (.aspx) and master pages (.master), stylsheets (.css), JavaScript (.js) etc. SPCop can be used directly in Visual Studio 2010/2012/2013 to analyse SharePoint projects.
NOTE: SPCop also includes all memory disposal rules previously checked by SPDisposeCheck. As SPCop also supports SP2013 assemblies (which SPDisposeCheck doesn't), we recommend that you use SPCop instead.
Read more about SPCAF and try it out on the website.
Use SPCop directly in Visual Studio
Get Errors and Warnings and open the files directly in VS
Download from Visual Studio Gallery
Comments (0)

Skip to main content