SharePoint 2013 supports both 14 and 15 hive, How to Upgrade

this article  includes:  How to deploy WSPs from SharePoint 2010 in SharePoint 2013

SharePoint 2010 Solutions in SharePoint 2013

How to upgrade wsp from SharePoint 2010 to SharePoint 2013

I had experience during migration from SharePoint 2010 to SharePoint 201 and findings from various posts about migration around the web.

Most of the wsp Solutions deployed in SharePoint 2010 should work fine in SharePoint 2013. This is because of the Support for both 14 Hive and 15 Hive directories that are created in SharePoint 2013 by default. When we installed SharePoint 2013

First time when we deploy a SharePoint 2010 Solution as usual like how we deploy in SharePoint 2010 it gets deployed to 14 Hive and not 15 Hive. To force the solution to get it deployed in 15 Hive you

We have two ways to deploy SharePoint 2010 wsp to SharePoint 2013

  1. We can modify manifest.xml file of our solution and add addSharePointVersion=”15.0″ attribute to it. The Solutions can be forced to install in 15 hive that way However, some of the files especially that refers to _layouts might not work. All SharePoint 2010 Solution files that refers to _layouts folder (i.e. Features, Layouts-files, Images, ControlTemplates)needs to be updated(best approach is to Re-Create the Solution in Visual Studio 2012).In 15 hive , files in Layouts directory has a Path with ’15′ added to it.

    For example path of a Custompage in 14 and 15 hive would be –
    14 Hive path  – _/layouts/ custmpage.aspx
    15 Hive  path – _/layouts/15/custmpage.aspx

We need to update the references of all the items we have deployed in 15 hives like features, layouts files, images, controlTemplate Notice if the solution is targeted to deployed in 15 Hive.

  1. CompetibilityLevel parameter of Install –SPInstall command we can now deploy our .wsp or Solution to either 14 hive, 15 hive or both using the Powershell itself This “Compatibility Level” value overrides SharePointProductVersion specified in manifest of the solution and it is only way with which solutions can be installed in both 14 & 15 Hive.

Compatibility Level Impacts only files deployed to the Templates folder in the 14/15 Root folder i.e. Features, Layouts-files, Images, ControlTemplates, etc.The files deployed Outside of this folder (e.g. a WCF Service) will be deployed to the 15/ISAPI regardless of the Manifest or PowerShell Compatibility level settings of the wsp-package. Files such as Assemblies in GAC/Bin and certain resource files will also be deployed to the same location regardless of the Compatibility Level.

Bin Directory Considerations –
Also, we can no longer add partial trust solution packages to the \bin directory. any files deployed to the \bin directory must be full trust.

GAC Considerations – After the Release of .NET Framework 4.0, the GAC was split into two, one for each CLR.
c:\windows\assembly is the location for .NET versions 1.0 through 3.5 and
c:\windows\\assembly is location for all the dlls for project Created in .NET Framework 4.0.
Consider looking into new Location if you have Created your project in Visual Studio 2012.
For these reasons and more it is recommended to Re-Create a Solution in Visual Studio 2012, Re-add all the features, Components and then deploy it to SharePoint 2013 in 15 hive.

Sandbox Solutions –

Actually Sandbox solution is depreciated in SharePoint 2013,Sandbox solutions are upgraded with the Content databases in SharePoint 2013, still we can create the sandbox solution but Microsoft does not support.

Fabulous 40 templates in SharePoint 2013 –

As per MSDN, Microsoft is not creating any New Versions of these Fabulous 40 Templates. The Old Sites based on these templates can be upgraded only if the Templates are installed successfully in SharePoint 2013.we can try installing wsp of Fab 40 with CompatabilityLevelas 15 and upgrade the existing site collections.

Master pages and CSS files –

Master Pages and Css has Changed a lot in SharePoint 2013.we can deploy a master page in Master page gallery but the styles from old core.css needs to be updated.

SharePoint Themes –

Re-create our themes following the SharePoint 2013 theming guidance, or select a new theme available in SharePoint 2013.

SharePoint Site definition –

Migrate sites to a supported, predefined site definition, and then apply Custom features by using Solution deployment. We can also continue to use a Custom site definition. We do not have to create a new site definition that is based on SharePoint 2013. happy coding:)

About Krishana Kumar

Krishana Kumar is SharePoint Architect/Trainer having Architecture experience with high volumes at Enterprise level and global scale - creation of highly scalable solutions with global user base and geographically distributed architectural components. Good knowledge of SharePoint best practices and governance models. I hold Two Master degree in Computer Science with over 11 years of experience working on Microsoft Technologies specially SharePoint, Project, .NET and other Information Worker Technologies. Having good exposer in Client side scripting Angular.js, backbone and Node. I am currently responsible for SharePoint Infrastructure set up and leading teams in various medium and large scale projects, architecting, designing & installing SharePoint farms, developing custom components,, and providing advanced SharePoint administration and development training to teams and customers. I regularly speaks in various SharePoint User Groups and other Events. I have MCSA Windows Azure, MCSA Office 365, MCSE & MCSD SharePoint 2013, Microsoft Certified Developer (MCD) and holds MCPD, MCTIP and MCTS for SharePoint 2010, MCTS MOSS 2007 & WSS 3.0, MCPD, MCITP (EPM 2010 & 2007) and MCSD .NET.
This entry was posted in General Interest. Bookmark the permalink.