UPDATE: Since 1st of June 2015 SPCop (later renamed into SPCAF Developer Edition) is no longer available in the Visual Studio. You can read about why we decided to remove it on the SPCAF blog. Thank you everyone for your support! All features and many, many more are included in both SPCAF Developer and SPCAF Professional Editions.
I’m happy and proud that after many years of work together with my fellow friend Torsten, last week I released the free SharePoint Code Check (SPCop) to the Visual Studio Extension Gallery.
SPCop is based on the SharePoint Code Analysis Framework (SPCAF) 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 errors in XML directly in Visual Studio and not only after a deployment to SharePoint and manual testing.
- We can now easier follow best practices and can learn how to develop better SharePoint solutions.
- We can analyze SharePoint specific .net Code
- We can extend SPCop/SPCAF with custom rules like the guys of the SPCAFContrib project on CodePlex are already doing
In the future also more rules for analysis of SharePoint apps will be added and will make it easier to develop high quality SharePoint apps.
SPDisposeCheck is dead!
UPDATE: Read a more detailed explanation why SPDisposeCheck should not be used in my blog “STOP using SPDisposeCheck (or MSOCAF) with SharePoint 2013! Now!”
One of the most recent additions in SPCop is the new rule category “Memory Disposal”
But wait, we have already SPDisposeCheck which is doing that, right? So why another tool…?
The problem, the last version of SPDisposeCheck was released in 2010 and was entirely focused on SharePoint 2010.
You might not be aware of it, but unfortunately, SPDisposeCheck was built with the .net Framework 3.5. This means that now, in the times of SharePoint 2013, this prevents it to analyze .net Framework 4.5 assemblies.
Also many rules in SPDisposeCheck caused false positives/negatives or are just outdated now. That’s why we implemented all still valid memory disposal rules ourselves based on the current guidance and our experience in SPCop/SPCAF.
So if you thought you were save because SPDisposeCheck does not show any errors in your SharePoint 2013 project, you better want to check with SPCop again…
Additionally, SPCop checks many more things which you can explore in the documentation.
See here how it works: