tag:help.appveyor.com,2012-11-13:/discussions/problems/2534-building-vs2015-rtm-solutionAppVeyor: Discussion 2018-10-19T08:17:20Ztag:help.appveyor.com,2012-11-13:Comment/374341102015-07-20T23:05:23Z2017-01-21T22:42:16ZBuilding VS2015 RTM solution<div><p>Hi,</p>
<p>Given that VS2015 RTM was released today (woo!) I'd like to
upgrade one of my open source projects and its build.</p>
<p>I've updated the code, but it seems that VS2012 is actually
performing the build.</p>
<p>I tried selecting the OS labelled "Visual Studio 2015 RC" and
setting the path to:</p>
<pre>
<code>set PATH=C:\Program Files (x86)\MSBuild\14.0\Bin;%PATH%</code>
</pre>
<p>However that hasn't helped and the log still shows VS 12.0
(VS2013) is attempting the build and failing on new C# 6 language
features.</p>
<p>When will there be an OS image for VS2015? Is there something I
can do to work around this problem for now?</p>
<p>The project in question is at: <a href="https://ci.appveyor.com/project/drewnoakes/metadata-extractor-dotnet">
https://ci.appveyor.com/project/drewnoakes/metadata-extractor-dotnet</a></p>
<p>Many thanks.</p></div>drewnoakestag:help.appveyor.com,2012-11-13:Comment/374341102015-07-20T23:20:15Z2015-07-20T23:20:15ZBuilding VS2015 RTM solution<div><p>Yeah, lot's of new stuff from Microsoft today - feels almost
like Christmas! :)</p>
<p>AppVeyor enforces MSBuild 12.0 because the solution is VS 2013:
<a href="https://github.com/drewnoakes/metadata-extractor-dotnet/blob/master/MetadataExtractor.sln#L3">
https://github.com/drewnoakes/metadata-extractor-dotnet/blob/master...</a>
- either convert it to VS 2015 or use your own "msbuild" command
without a path.</p>
<p>Regarding the image - <code>Visual Studio 2015 RC</code> is
correct and <code>Visual Studio 2015</code> will be available
tomorrow. However, I've just moved your account to a new
environment where VS 2015 is installed by default, so you don't
need an image.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/374341102015-07-21T12:01:45Z2015-07-21T12:01:45ZBuilding VS2015 RTM solution<div><p>I felt there is no need to create another thread since I have
the same problem.</p>
<p>I converted solution header to the following (RTM is "14", not
"2015"):<br>
Microsoft Visual Studio Solution File, Format Version 12.00</p>
<h1><a class="anchor" name="visual-studio-14" href="#visual-studio-14"></a>Visual Studio
14</h1>
<p>VisualStudioVersion = 14.0.23107.0<br>
MinimumVisualStudioVersion = 10.0.40219.1</p>
<p>Set "os" to "Visual Studio 2015 RC"</p>
<p>And it still uses "Microsoft (R) Build Engine version
12.0.31101.0", failiing builds with new C# 6 syntax :(</p></div>Aristarkh Zagorodnikovtag:help.appveyor.com,2012-11-13:Comment/374341102015-07-21T16:05:13Z2015-07-21T16:05:13ZBuilding VS2015 RTM solution<div><p>Add this to <code>install</code> or <code>before_build</code>
section:</p>
<pre>
<code>set PATH=C:\Program Files (x86)\MSBuild\14.0\Bin;%PATH%</code>
</pre></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/374341102015-07-21T16:48:58Z2015-07-21T16:48:58ZBuilding VS2015 RTM solution<div><p>Thanks, Feodor, your support is as great as always.<br>
Is setting path a temporary measure that should not be needed after
images will be updated or should I just bake it into the .yml
permanently for VS 2015 builds?</p></div>Aristarkh Zagorodnikovtag:help.appveyor.com,2012-11-13:Comment/374341102015-07-21T19:22:03Z2015-07-21T19:22:03ZBuilding VS2015 RTM solution<div><p>Yes, add it into appveyor.yml.</p>
<p>We don't expect all customers migrating to VS 2015 in one
night/week, so MSBuild 12.0 will be default in PATH for a
while.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/374341102015-07-21T19:49:30Z2015-07-21T19:49:32ZBuilding VS2015 RTM solution<div><p>We would like to migrate to VS 2015 also, can you move our
account?</p></div>Jeremiah Gowdytag:help.appveyor.com,2012-11-13:Comment/374341102015-07-21T19:52:17Z2015-07-21T19:52:17ZBuilding VS2015 RTM solution<div><p>Done. There is still RC, RTM will be available later today.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/374341102015-07-21T22:51:16Z2015-07-21T22:51:16ZBuilding VS2015 RTM solution<div><p>please migrate me to the default 2015 image as well. thank
you!</p></div>christag:help.appveyor.com,2012-11-13:Comment/374341102015-07-22T05:08:31Z2015-07-22T05:08:31ZBuilding VS2015 RTM solution<div><p>@Chris - what's account name that should be migrated?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/374341102015-07-22T13:48:41Z2015-07-22T13:48:41ZBuilding VS2015 RTM solution<div><p>@Feodor my account name is Authenticom ...thanks!</p></div>christag:help.appveyor.com,2012-11-13:Comment/374341102015-07-22T16:48:42Z2015-07-22T16:48:42ZBuilding VS2015 RTM solution<div><p>Moved.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/374341102015-07-22T17:50:05Z2015-07-22T17:50:05ZBuilding VS2015 RTM solution<div><p>thanks @Feodor! I seem to still be having an issue though. I've
set the following in both the environment install and the before
build events, but is still uses v12</p>
<pre>
<code>set PATH=C:\Program Files (x86)\MSBuild\14.0\Bin;%PATH%</code>
</pre>
<p>I've tried the default image and manually selecting the VS 2015
azure image...same results for both.</p></div>christag:help.appveyor.com,2012-11-13:Comment/374341102015-07-22T17:51:54Z2015-07-22T17:51:54ZBuilding VS2015 RTM solution<div><p>If your project build step is set to "MSBuild" make sure .sln
file has <code># Visual Studio 14</code> header (not <code># Visual
Studio 2013</code>); otherwise AppVeyor will force MSBuild
12.0.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/374341102015-07-27T07:49:27Z2015-07-27T07:49:27ZBuilding VS2015 RTM solution<div><p>Could the "d3-x" account be moved also?</p></div>Aristarkh Zagorodnikovtag:help.appveyor.com,2012-11-13:Comment/374341102015-07-27T17:04:32Z2015-07-27T17:04:32ZBuilding VS2015 RTM solution<div><p>Moved.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/374341102015-07-28T08:41:23Z2015-07-28T08:41:23ZBuilding VS2015 RTM solution<div><p>Thank you, Feodor!</p></div>Aristarkh Zagorodnikovtag:help.appveyor.com,2012-11-13:Comment/374341102015-07-28T15:12:50Z2015-07-28T15:12:51ZBuilding VS2015 RTM solution<div><p>When do you expect that the VS 2015 image will be as fast to
queue as the Windows Server 2012 image?</p>
<p>Thanks!</p>
<p>James</p></div>James Whitetag:help.appveyor.com,2012-11-13:Comment/374341102015-07-28T17:15:08Z2015-07-28T17:15:08ZBuilding VS2015 RTM solution<div><p>We had to convert one of our projects to use VS2015 (used os:
Visual Studio 2015) but now it takes much longer to build. Our
other project is broken because it depends on this one but the
build will time out if it has to run on such a slow machine. Is
there a way to get VS2015 on the same fast machines we were using
for VS2013?</p>
<p>Thanks!</p></div>Michael Shermantag:help.appveyor.com,2012-11-13:Comment/374341102015-07-28T18:37:14Z2015-07-28T18:37:14ZBuilding VS2015 RTM solution<div><p>VS 2015 on Pro environment will be available this week. We can
move you to OSS environment for now with VS 2015 installed?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/374341102015-07-28T18:42:12Z2015-07-28T18:42:13ZBuilding VS2015 RTM solution<div><p>I hope all of my fellow AppVeyor customers are aware of the
fatal defects in the RyuJIT of .NET 4.6. If you have .NET 4.6
installed (including by installing Visual Studio 2015) then even
your .NET 4.5 and other projects will use the new JIT. The new JIT
in Release Mode generates incorrect / defective code. This is a
known issue with .NET 4.6 with no fix currently.</p>
<p>Since this is a JIT issue, it should affect only the runtime of
your software, not the compilation which AppVeyor provides.</p>
<p>Blog: <a href="http://nickcraver.com/blog/2015/07/27/why-you-should-wait-on-dotnet-46/">
http://nickcraver.com/blog/2015/07/27/why-you-should-wait-on-dotnet...</a></p>
<p>KB: <a href="https://support.microsoft.com/en-us/kb/3065367">https://support.microsoft.com/en-us/kb/3065367</a></p>
<p>POC: <a href="https://github.com/StackExchange/RyuJIT-TailCallBug">https://github.com/StackExchange/RyuJIT-TailCallBug</a></p>
<p>Second defect: <a href="https://github.com/dotnet/coreclr/issues/1299">https://github.com/dotnet/coreclr/issues/1299</a></p></div>Jeremiah Gowdytag:help.appveyor.com,2012-11-13:Comment/374341102015-07-28T18:52:23Z2015-07-28T18:52:23ZBuilding VS2015 RTM solution<div><p>There are breaking changes in BCL as well. Take this issue with
Service Bus for example: <a href="http://stackoverflow.com/questions/28333034/how-do-i-report-a-bug-in-windows-server-service-bus">
http://stackoverflow.com/questions/28333034/how-do-i-report-a-bug-i...</a></p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/374341102015-07-28T18:54:41Z2015-07-28T18:54:42ZBuilding VS2015 RTM solution<div><p>Thanks, Feodor. I’ve got a workaround now that we can use
to stick with VS2013 for now so we’ll just wait until your
scheduled upgrade.</p>
<p>Regards,</p>
<p>Sherm</p></div>msherman