How to upgrade a SharePoint farm solution to 2013

Original address: How to upgrade a custom application to SharePoint 2013

How to upgrade SharePointFarm Solutions to -on

If you putSharePoint2010Farm Solutions(WSPfile)Install to,He can use it to a large extent. Well, this is probably becauseMicrosoftdeploy all of the support forSharePoint2010the file to theHive. When you deploy the solution, ifmanifest.xmlinclude'sharepointversion= "14.0",SharePointwill be deployedlayouts, featuresWait until the old14.0 hive.if it's marked'sharepointversion= "15.0",SharePointwill be deployed to the newHive.

If you just want to be in -can be used, then this function is useful. If, like us, you want to fully supportSharePoint2013and fully comply with. Net 4.0, you need to keep looking down. Finally in -There are some good new features you can benefit from.

Upgrade Steps

here is a list of all the work I need to do to run the solution. If you need to upgrade the farm solution to , and also to support , then you will find it useful.

Supportin aVisualStudio Solutionmultiple versions are supported in

This requires a lot of steps, I wrote a separate document ' How to support multiple versions of SharePoint in a single visuals ... '. I suggest you read this article and come back and read on.

Change your solution package into' 15.0 '

The first change you need to make is to set ' sharepointproduct Version ' into " 15.0 ". This will allow your solution to be treated as SharePoint2013 solution, and all components are deployed to the right place.  

who's moving?GAC?

LetSharePoint DevelopersOne of the biggest surprises of surprise was that Microsoft decided to moveGAC (Global Assembly Cache)to a new location..If you are inDebug, the new version of theAssemblyput inGAC,you need to know,GACit's changed position.!put inC:\windows\assemblyand then try' Attach to process 'It's not a good use.
now, each version of theMicrosoft.NETall have aGACthe folder(v4.0and the above version). The oldGACIt's still there, but it's reserved for the lower version.. NETwas used.

Why should there be a new GAC it? If you want to see more in-depth discussion, See this post.

sputility. Getgenericsetuppathmethod was abandoned.

This may surprise you. If you continue to use sputility.getgenericsetuppath (), He will return to Hive (SharePoint), instead of the new Hive (SharePoint). So if you use this method to get files, you are likely to get them. The new method is to call sputility.getversionedgenericsetuppath (). We support all 3 versions of SharePoint by using the following methods and parameters :

_layoutsThe virtual directory has a the

If you have code access ' _layouts ' folder, you need to use the correct version. Look at the picture below and you'll notice that, in fact,there's actually a folder calledlayouts in the inside of the box .

Here's an example to illustrate how this affects your code. This code returns the URL of a page deployed to the layouts folder . If we did not modify the code to include It, it would be a good thing to return to the 14hive– solution, but solution is not good.

the others wereSharePoint2013Waste of

· You can access Technet to get The list that was discarded in SharePoint2013.

Postedby Markjones on February-at

View Blog

How to upgrade a SharePoint farm solution to 2013