Creating a SharePoint package is easy enough with Visual Studio but each time you restart it, the package location used previously is replaced with the default location of the current user’s Documents folder.<\/p>\n
To save a few seconds from my life I decided to write a PowerShell script to build and package the solution, meaning I no longer have to specify the publish location whenever Visual Studio is restarted.<\/p>\n
I’m using Visual Studio 2013 and SharePoint 2013<\/p>\n
\r\n& \"C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\msbuild.exe\" \"C:\\Projects\\TestProject\\TestSolution.csproj\" \/t:rebuild;package\r\n\r\nWrite-Host \"Copying TestSolution.wsp to Packages folder\" -NoNewLine\r\nCopy-Item -Confirm:$false \"C:\\Projects\\TestProject\\bin\\Debug\\TestSolution.wsp\" C:\\Packages\\\r\nWrite-Host \" - done.\"\r\n<\/pre>\nThe script shown has been simplified for this post and is easy enough to parametrise to allow you to specify different SharePoint projects to package.<\/p>\n
Anyway, back to the main reason for this post.<\/p>\n
After doing the above and running the script the following error was generated:<\/p>\n
C:\\Projects\\TestProject\\TestSolution.csproj(88,3): error MSB4019: The imported project “C:\\Program Files (x86)\\MSBuild\\Microsoft\\VisualStudio\\v10.0\\SharePointTools\\Microsoft.VisualStudio.SharePoint.targets” was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.<\/em>
\n
\nThe thing that immediately stood out for me was the mention of v10 of Visual Studio. I’m using VS 2013, so this should be v12.<\/p>\nBoth Visual Studio 2012 and 2013 allow opening and building of 2010 solutions. To achieve this VS injects the current version when building from the IDE but when running from the command line, msbuild does not know which version to use so is defaulting to v10. Which is exactly what would happen when trying to build the project from VS 2010, it would simply default to v10 as no version number injection would occur in this version of the IDE.<\/p>\n
The easy fix for this is to add an additional argument to the msbuild command:<\/p>\n
\r\n& \"C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\msbuild.exe\" \"C:\\Projects\\TestProject\\TestSolution.csproj\" \/t:rebuild;package \/p:VisualStudioVersion=12.0\r\n\r\nWrite-Host \"Copying TestSolution.wsp to Packages folder\" -NoNewLine\r\nCopy-Item -Confirm:$false \"C:\\Projects\\TestProject\\bin\\Debug\\TestSolution.wsp\" C:\\Packages\\\r\nWrite-Host \" - done.\"\r\n<\/pre>\nHere I’m setting the argument VisualStudioVersion<\/em> to 12. For Visual Studio 2012 this would be set to 11.<\/p>\n","protected":false},"excerpt":{"rendered":"Creating a SharePoint package is easy enough with Visual Studio but each time you restart it, the package location used previously is replaced with the default location of the current user’s Documents folder. To save a few seconds from my … Continue reading