tag:help.appveyor.com,2012-11-13:/discussions/problems/105-missing-azure-sdk-22-targetsAppVeyor: Discussion 2018-08-25T01:38:45Ztag:help.appveyor.com,2012-11-13:Comment/317351112014-02-21T18:26:47Z2014-02-21T18:26:47ZMissing Azure SDK 2.2 targets<div><p>Hi Chris,</p>
<p>Azure SDK 2.2 is there.</p>
<p>While trying to build Azure Cloud Service project you may get
the following (or similar related) error:</p>
<pre>
<code>The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\vX.X\Windows Azure Tools\2.X\Microsoft.WindowsAzure.targets" was not found.</code>
</pre>
<p>To fix this error on <strong>Environment</strong> tab of project
settings add the following environment variable:</p>
<pre>
<code>VisualStudioVersion 12.0</code>
</pre>
<p>where 12.0 is the version your Visual Studio (VS 2013 - 12.0, VS
2012 - 11.0, VS 2010 - 10.0).</p>
<p>I added some more details on this page: <a href=
"http://www.appveyor.com/docs2/build-phase">http://www.appveyor.com/docs2/build-phase</a></p>
<p>Let me know how it goes.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/317351112014-02-21T18:56:51Z2014-02-21T18:56:51ZMissing Azure SDK 2.2 targets<div><p>Yes, after looking further into the errors I realized that it
was looking under the wrong version of VS for the targets and I
added the environment variable and it solved the issue. I am sorry
about posting so quickly, I should have done some more looking
before I did.</p>
<p>in the case of VS2013 solutions if you ran MSBuild 12.0 you
wouldn't have this issue.</p>
<p>Of course this is a double edged sward because running MSBuild
12.0 against VS 2012 solutions can cause an invalid
TargetFrameworkMonikor error on deploy of the generated webdeploy
package.</p></div>christag:help.appveyor.com,2012-11-13:Comment/317351112014-02-21T19:00:20Z2014-02-21T19:00:20ZMissing Azure SDK 2.2 targets<div><p>Thanks for the update!</p>
<p>I agree with you the problem is tightly related to selecting
correct <code>msbuild</code> for the given VS version. It's clear
starting from VS 2013 we should run msbuild 12.0.</p>
<p>I'm going to continue discussion in your another thread.</p></div>Feodor Fitsner