Migrating Code from MOSS 2007 to SharePoint 2010

There is a lot of buzz in the market to move towards new and exciting SharePoint 2010. Same is the headache for SharePoint developers how to move the code to new structure.

 

Two tools are popularly used in the market to build WSPs are

  1. WSPBuilder
  2. Visual Studio templates for SharePoint 2010

 

WSPBuilder was popular tool with MOSS 2007 developers, but it’s author hasn’t updated since long. Last release was on January 2010.

 

Visual Studio templates for SharePoint 2010 are integrated in Visual Studio 2010 and can be used for better integration. It alone by itself is not so useful. There is an add-on CKSDEV enhances the functionalities of it. With this extensions it becomes as good as WSPBuilder.

 

Which tool is better to use is a matter of personal choice and I will left it on individual.

 

Back to the main topic of migration.

 

I have found two useful methods of migrating code faster from MOSS 2007 to SharePoint 2010. None of them is 100%, but it definitely helps with most of the manual tasks.

 

  1. Import SharePoint Solution Package

    If you have WSP for the code, Visual studio 2010 provides an option of importing WSP. Now this is interesting as it does not rely on which tool is used to generate WSP. As long as WSP is properly built, we are good to go.

    Import SharePoint Solution Package

    Import SharePoint Solution Package

  2. Import WSPBuilder Project
    If you have MOSS 2007 WSPBuilder project structure, then this comes handy. Just follow the steps and you are good to go.

    Import WSPBuilder Project

    Import WSPBuilder Project

 

Even though none of these method is perfect (at least for the projects I was trying!), these methods migrated code more than 90% properly. Once it is done with migration, we still need to go and cross verify the code items.

 

Hope this helps.

10 Comments »

RSS feed for comments on this post. TrackBack URL


Leave a Reply