It takes a WSP solution with full trust code and provides guidance, how this code could be migrated by using a modern approach with CSOM or App Model.

Learn more about it:

Short Demo Video

Jeremy Thake interviewing Matthias Einig in his Office Podcast

Download the free SharePoint Code Migration Assessment tool

Product page

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

• SharePoint solutions (.wsp) for SharePoint 2007 / 2010 / 2013
• SharePoint 2013 apps

Download the binaries, source code and some test applications: https://modernuicharts.codeplex.com/

Or directly try them in the Silverlight application: https://www.mossblogger.de/charts/

Intention 1
I needed Modern UI Charts for my own application which should run on Desktop (WPF), Web (Silverlight) and Windows 8 devices and I didn't want to use 3 different third party charting components. That’s why I created the charts from scratch and used them in the tool “SharePoint Code Analysis Framework (SPCAF)” (https://go.spcaf.com/VSGallery) which I have developed with Matthias Einig.

Intention 2
I think that XAML is the greatest way to "describe” the UI of an application via a markup language. I don’t want to miss things like data binding, styling of controls, data templates, animation of state changes, easy re-use of custom controls, design support with Blend and many more. I don’t hope that HTML5 and JavaScript are the only future for our UIs. That’s why I wanted to discover how the same XAML could be used “cross-plattform” in WPF, Silverlight and Windows 8. For the charts I wanted to use as much as possible of the same XAML code which is available on all these plattforms. So finally the code for the charts uses the lowest common XAML subset of all three worlds. Check out the sample application in this project and see how it works.

Features

Dark Layout

Custom Color Palette e.g. with gradients, mono chrome

Get it here as BETA.

The SharePoint Code Analysis Framework (SPCAF) provides tools to analyze SharePoint code. This includes

• SharePoint solutions (.wsp) for SharePoint 2007 / 2010 / 2013
• SharePoint 2013 apps

SPCAF 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) etc.

SPCAF can be used directly in Visual Studio 2012 or 2010 to analyze SharePoint projects. It also provides a client application to analyze existing WSP packages, can be integrated into a Team Build via a custom build activity, it can be run on command line or as MSBuild task during each local build.

Use SPCAF directly in Visual Studio

Get Errors and Warnings and open the files directly in VS

Visualize Dependencies

Use the client application to analyze existing WSPs or APPs

Highlights

• Contains ~300 rules to validate SharePoint code for correctness, solution design, best practices etc..
• Creates dependency diagrams in DGML to visualize dependencies within SharePoint code
• Can be seamlessly integrated into your development process
• Provides a client application to analyze WSP and APP files.
• Can also be run during a Team Build (supports TFS 2010 and TFS 2012)
• Can be extended with custom rules or custom metrics

Sample analysis results

• Rules reports shows errors and warnings Open sample report
• Dependency diagram visualizes package dependencies Open sample report
• Inventory reports lists all contents of the packages Open sample report
• Metric reports shows complexity and amount of elements in the code Open sample report

Who should use it?

• SharePoint Architects can ensure proper application design and detect violations against best practices
• SharePoint Developers can ensure that their code is correct and that errors in XML code can be found early directly in Visual Studio and not only after deployment to SharePoint.
• SharePoint Quality Assurance can ensure that WSP packages are developed according to the best practices and the e.g. Customization Policies are not violated.
• IT Pros can ensure that the WSP files does not contain “dangerous” code and that they can install the packages without fear. The inventory reports gives a detailed overview about the contents in the packages and is a good documentation of the code.

Risk of Customizations

Sometimes this extensibility is good and sometimes it is bad. Inappropriate customization can lead to a SharePoint environment, which cannot be managed anymore. Performance problems, crashed environments and unsatisfied users are the results. And often the migration to newer versions of SharePoint is impossible because of these customizations which leads to huge efforts to migrate at least the stored data in SharePoint.

Rules and Policies

But prohibit the customization of SharePoint is not an option for many companies because this would constrain the potenzial of SharePoint. So we need to find a way to customize SharePoint but prevent that the code impacts SharePoint in negative ways.

One way is to establish rules, conventions and policies which define how SharePoint customization must happen and also which type of customization is not allowed. These rules and policies must be defined (e.g. in customization policies) and must be accepted by all involved people, like developers, architects and also by the business side because these policies may limit the adaptability of SharePoint.

You cannot manage what you cannot measure

When these policies and rules are defined they must be controlled and measured, ideally with tools for code analysis, like FxCop, StyleCop, FxCop Metrics, SPDisposeCheck, CAT.NET etc. However, all these tools have one crucial limititation: they cannot analyze SharePoint XML code. The tools can only analyze assemblies and C# source code, but they cannot find errors or issues in the XML of Features, Content Types, Solution packages, Site Definitions etc. The tools can also not analyze the solution packages and can not detect if a SharePoint system file is overridden during depoyment.

Thats why SharePoint Code Analysis Framework (SPCAF) has been developed: SPCAF "reads" SharePoint solution packages (.WSP) and "converts" the SharePoint XML into an analyzable structure. This new structure of the code is used by 4 major tools to analyze der SharePoint code:
•SPCop checks the code for violations against more than 300 rules.
•SPMetrics calculates SharePoint code metrics and helps for instance to measure the complexity of the code.
•SPDepend analyzes dependencies between the SharePoint artefacts (like Features, ContentTypes etc.) and detects dependencies to external components.
•SPInventory creates a detailed inventory of all elements in SharePoint packages.

These tools can be used by architects, developers, qualiy managers or IT operators to ensure that SharePoint code is conform to their customization policies and conventions.

People behind

The SharePoint Code Analysis tools have been developed by Torsten Mandelkow and Matthias Einig. Both are working since many years as consultants, architects and developers in SharePoint development projects. During their work they were faced with lots of problems in SharePoint development and started to develop tools for their own to make SharePoint development easier and faster and to improve the quality of SharePoint code. Some of these tools have been published and some of them can be found on codeplex.com.