Installing VseWSS upgrade template for Visual Studio 2010
Visual Studio 2010 comes with a really great set of SharePoint 2010 templates for SharePoint development. All of you who have developed in Visual Studio 2005 and 2008 for SharePoint 2007 will agree that this set of templates makes our lives as SharePoint developer so much easier!
One of the tools we could use for SharePoint 2007 development was VseWSS. This tool added a lot of metadata to the project and was a pain if you wanted to open it on another machine that hadn’t VseWSS installed. Paul Andrew and his team have been working on an upgrade template to upgrade VseWSS projects to Visual Studio 2010. You can download it here.
But before you can start working with this upgrade template, you have to get it installed… and the explanation on the download page is far from complete. Here are the steps that I executed to get the upgrade template installed:
- Download the VSeWSS_Upgrade_Sample_Beta_20100108.msi installer.
- Be sure to close all instances of Visual Studio 2010 before you start installing the template.
- Run the installer.
- Open Windows Explorer and browse to C:\Program Files (x86)\Microsoft\VSeWSS Upgrade.
- You will find another MSI that you need to execute first: VSeWSSUpgrade_Beta2_20091203.msi.
- Open a Visual Studio command prompt as administrator.
- Execute DEVENV /installvstemplates.
- Start Visual Studio 2010.
- Create a new project and choose the Import VseWSS project template.
- In the first step of the import wizard you have to specify the SharePoint URL to where you want to deploy. You also have to specify if you want a farm solution or a sandboxed solution. Think before you act🙂
- In the second step of the import wizard you have to specify the location of the VseWSS project you want to upgrade.
And there your go🙂
If you need more information on the upgrades done by the upgrade template, you can read the README file which is installed together with the MSI in the C:\Program Files (x86)\Microsoft\VSeWSS Upgrade folder.
Once installed, the template works as magic: your project is converted to a SharePoint 2010 project. But the golden rule is to verify your new project before deploying it to SharePoint 2010 because it needs some (minor) tweeks before it is ready to deploy.