Here is the scenario for this silly issue that bugged me for a while after migrating my Azure solution to SDK. But first let me tell you that I was working mainly in VS 2010 and just recently migrated to VS 2013 days after it release. Some more days later I upgraded the Azure solution to SDK version 2.2. As you may know, that one dropped support for VS 2010. I am making use of Visual Studio Online (previously known as Team Foundation Service) . Since the upgrade all my builds started to fail on Visual Studio Online (they were working ok locally) – I though that maybe the VSO servers did not have the recently released Azure SDK 2.2 binaries… silly me.
After some time and futile search efforts I decided to have a look again. I found the following on the Azure solution file:
<PropertyGroup>
<VisualStudioVersion Condition=" '$(VisualStudioVersion)' == '' ">10.0</VisualStudioVersion>
<CloudExtensionsDir Condition=" '$(CloudExtensionsDir)' == '' ">$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v$(VisualStudioVersion)\Windows Azure Tools\2.2\</CloudExtensionsDir>
</PropertyGroup>
<Import Project="$(CloudExtensionsDir)Microsoft.WindowsAzure.targets" />
As you can see, the target is being searched in the VS 2010 directory (which does not have support for SDK 2.2). Changing the version to 12.0 fixed the issue!!
