tag:help.appveyor.com,2012-11-13:/discussions/problems/2522-windows-server-2012-environment-now-using-msbuild-2014-by-defaultAppVeyor: Discussion 2015-07-20T21:09:02Ztag:help.appveyor.com,2012-11-13:Comment/374198312015-07-19T02:58:37Z2015-07-19T03:22:26ZWindows Server 2012 environment now using MSBuild 14 by default<div><p>A recent build is now running MSBuild version 14.0.22823.1 -
it's triggering a compiler error, but that's not your problem:</p>
<p><a href="https://ci.appveyor.com/project/Haacked15676/octokit-net/build/1.0.1105#L43">
https://ci.appveyor.com/project/Haacked15676/octokit-net/build/1.0....</a></p>
<p>Contrast that with a previous build which chooses the right
version:</p>
<p><a href="https://ci.appveyor.com/project/Haacked15676/octokit-net/build/1.0.1074#L41">
https://ci.appveyor.com/project/Haacked15676/octokit-net/build/1.0....</a></p>
<p>I gather some other pre-requisite has been added in between.</p>
<p>Setting PATH on install like this doesn't seem to change the
behaviour either (perhaps I can do something in my FAKE script to
address this):</p>
<pre>
<code>set PATH=C:\Program Files (x86)\MSBuild\12.0\Bin;%PATH%</code>
</pre>
<p>EDIT: another thing that's not working for me is <a href="https://github.com/octokit/octokit.net/commit/2cd0a37f386bac54e28ef51a67b7fb438187b9f1">
this commit</a> which was adapted from <a href="http://stackoverflow.com/questions/27989758/using-a-specific-version-of-msbuild-in-a-fake-build-script">
this SO thread</a></p></div>Brendan Forstertag:help.appveyor.com,2012-11-13:Comment/374198312015-07-19T20:05:39Z2015-07-19T20:05:39ZWindows Server 2012 environment now using MSBuild 14 by default<div><p>Right, <code>Haacked15676</code> account jas been moved to a new
environment where workers have Visual Studio 2015 RC installed.</p>
<p>If you look at this test build you'll see that there is only
MSBuild 12.0 in the path:<br>
<a href="https://ci.appveyor.com/project/FeodorFitsner/simple-console/build/1.0.627">
https://ci.appveyor.com/project/FeodorFitsner/simple-console/build/...</a>
and AppVeyor doesn't enforce MSBuild version in any way here.</p>
<p>Looks like it's FAKE picking up the most recent version of
MSBuild found on the machine. It might the right time to figure out
how to make it use MSBuild 12.0. Maybe there is a switch or
something.</p>
<p>Going forward we'll be migrating all projects to build workers
with VS 2015 and VS 2013 installed. Next week we'll be deploying a
new image with VS 2015 RTM. Your experience may help others using
FAKE on AppVeyor.</p>
<p>Let me know about your findings or questions.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/374198312015-07-19T22:20:05Z2015-07-19T22:20:05ZWindows Server 2012 environment now using MSBuild 14 by default<div><p>Thanks for the context Feodor. Should I be choosing a specific
image for this project? (I see a bunch of pre-release images but
nothing for VS2013 or VS2015)</p>
<p>I'll try a few other things and bug the FAKE team about how to
hook into that MSBuild detection.</p></div>Brendan Forstertag:help.appveyor.com,2012-11-13:Comment/374198312015-07-19T23:12:10Z2015-07-19T23:12:10ZWindows Server 2012 environment now using MSBuild 14 by default<div><p>Well, you can choose <code>Default Azure</code> with VS 2013 to
get where it was before moving to a new environment... and bug FAKE
team of course. We want to have a single image with VS 2013 and VS
2015 for all OSS accounts.</p></div>Feodor Fitsner