I was strugling to figure out what was wrong with my svn copy of the Orchard project, which was just updated through SVN.
When I ran the "ClickToBuildAzurePackage.cmd" command line tool, it kept erroring out.
When the Windows Azure SDK November 2011 version was released I updated the version to that, but I could not connect the dots that it could be the issue.
The updated SDK renames the "CloudService.targets" to "WindowsAzure.targets" and other related updates in the November 2011 release.
The error seems to have originated because, I had the svn for months and after running an update command through the TortoiseHg, I assumed I have the latest copy but it seems many of the files were removed added and deleted and my copy was in essense not upto date.
I tried running the "ClickToBuildAzurePackage.cmd" but it resulted in errors and it seems the errors were because of the issue with new directories not being mapped in the "AzurePackage.proj" file.
Origial value:
<Import Project="$(MSBuildExtensionsPath)\Microsoft\Cloud Service\1.0\Visual Studio 10.0\Microsoft.CloudService.targets" />
Updated value:
<Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v$(VisualStudioVersion)\Windows Azure Tools\1.6\Microsoft.WindowsAzure.targets" />
When you don't update the svn and it gets such issues than the best option is to delete the svn and start over by cloning the svn copy again. That's what I ended up doing, to resolve my issue.
When I ran the "ClickToBuildAzurePackage.cmd" command line tool, it kept erroring out.
When the Windows Azure SDK November 2011 version was released I updated the version to that, but I could not connect the dots that it could be the issue.
The updated SDK renames the "CloudService.targets" to "WindowsAzure.targets" and other related updates in the November 2011 release.
The error seems to have originated because, I had the svn for months and after running an update command through the TortoiseHg, I assumed I have the latest copy but it seems many of the files were removed added and deleted and my copy was in essense not upto date.
I tried running the "ClickToBuildAzurePackage.cmd" but it resulted in errors and it seems the errors were because of the issue with new directories not being mapped in the "AzurePackage.proj" file.
Origial value:
<Import Project="$(MSBuildExtensionsPath)\Microsoft\Cloud Service\1.0\Visual Studio 10.0\Microsoft.CloudService.targets" />
Updated value:
<Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v$(VisualStudioVersion)\Windows Azure Tools\1.6\Microsoft.WindowsAzure.targets" />
When you don't update the svn and it gets such issues than the best option is to delete the svn and start over by cloning the svn copy again. That's what I ended up doing, to resolve my issue.
Comments
Post a Comment