SharePoint 2013 Tool: Analysis code for WSP and APP

In SharePoint, most of the customization can be achieved without developing/writing custom solution. Some time we required a customization and during this customization the main concern on quality solution; we ensure the best practice & rules must be defined and follow.

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.

So there is no such a automated process that validate those rules during development face.

To deliver the quality standards as end result during earlier development face. Tool is created by Matthias Einig and Torsten Mandelkow and name of the tool is SharePoint Code Analysis Framework(SPCAF).

SPCAF Essential tool to ensure SharePoint code quality. SPCAF will analyze assemblies and all the XML for your SharePoint packages (wsp’s), and all other controls and master pages that are present in your package, it will help you improve your code or at least make it easier to check for errors.

To read more about the tool please read the documentation of SPCAF tool, you can download the trail version.

As per the documentation the code covers the following version.

SharePoint solution (.WSP) for SharePoint 2007/2010/2013
SharePoint 2013 Apps

The code within .wsp and .app files is extracted and the contained files are analyzed by the SharePoint code analyzer. This includes:

SharePoint artefacts in XML files, like Features, ContentTypes, ListTemplates
Assemblies (.dll)
ASP.NET files, like controls (.ascx), pages (.aspx) and master pages (.master)

You can download the SPCAF beta version. To know more about the SPCAF see its official site http://www.spcaf.com/

You can also download the free version of SPCop. The SPCop is just one component of SPCAF.

Comments

SharePoint RPC Protocols Examples Using OWSSVR.DLL

What is SharePoint RPC Protocols? Part 1 This reference includes information about the methods and usage of SharePoint Foundation Remote Procedure Call (RPC) protocol. This protocol can be used in Win32-based applications or in ASPX applications to make HTTP POST requests to the server. Methods in this protocol that do not modify the contents of the database can also be used in URL protocol to make HTTP GET requests. Definition taken from http://msdn.microsoft.com/en-us/library/ms448359.aspx You will find the OWSSVR.DLL in SharePoint 2010 Server Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI and MOSS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI OWSSVR.DLL List of commands DialogView Display ExportList GetProjSchema GetUsageBlob HitCounter RenderView To read more about the OWSSVR.DLL command Please read the URL Protocol from Microsoft Blog having a URL http://msdn.microsoft.com/en...

SharePoint 2013 Search Database Part 1

SharePoint 2013 Search architecture drastically change, as earlier in FS4SP 2010 we have 2 search applications “FASTContentSSA” and “FASTQuerySSA” and 7 total database in use. Following are the List of DB (FS4SP) FASTContentSSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTQuerySSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTSearchAdminDatabase : Fast Search Admin Database In SharePoint 2013 search has only 1 Search Service application and 4 database in use. No property store database need any more, now the properties are directly stored inside the index component and all the index directly indexed to the physical system where FS4SP data comes from database as well as from the File system now data directly stored and indexed/ retried from the Physical disk because of this performance increase and search experien...

STS CryptographicException Error : Key set does not exist

Common mistakes Both SharePoint Site and SSO Site NOT running on the same application pool. Application pool identity user doesn’t have permission to access the certification. Solution to this problem Set the same identity pool to : 2. Be sure to grant rights to the certificate for the App Pool running the web service Start -> Run -> MMC File -> Add/Remove Snapin Add the Certificates Snap In Select Computer Account, then hit next Select Local Computer (the default), then click Finish On the left panel from Console Root, navigate to Certificates (Local Computer) -> Personal -> Certificates You're certificate will most likely be here. Right click on your certificate -> All Tasks -> Manage Private Keys Set you're private key settings here. Add app pool account Reset iis

SharePoint For Developers

Search This Blog