Building VS2015 RTM solution
Hi,
Given that VS2015 RTM was released today (woo!) I'd like to upgrade one of my open source projects and its build.
I've updated the code, but it seems that VS2012 is actually performing the build.
I tried selecting the OS labelled "Visual Studio 2015 RC" and setting the path to:
set PATH=C:\Program Files (x86)\MSBuild\14.0\Bin;%PATH%
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.
When will there be an OS image for VS2015? Is there something I can do to work around this problem for now?
The project in question is at: https://ci.appveyor.com/project/drewnoakes/metadata-extractor-dotnet
Many thanks.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 20 Jul, 2015 11:20 PM
Yeah, lot's of new stuff from Microsoft today - feels almost like Christmas! :)
AppVeyor enforces MSBuild 12.0 because the solution is VS 2013: https://github.com/drewnoakes/metadata-extractor-dotnet/blob/master... - either convert it to VS 2015 or use your own "msbuild" command without a path.
Regarding the image -
Visual Studio 2015 RCis correct andVisual Studio 2015will 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.2 Posted by Aristarkh Zagor... on 21 Jul, 2015 12:01 PM
I felt there is no need to create another thread since I have the same problem.
I converted solution header to the following (RTM is "14", not "2015"):
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 14
VisualStudioVersion = 14.0.23107.0
MinimumVisualStudioVersion = 10.0.40219.1
Set "os" to "Visual Studio 2015 RC"
And it still uses "Microsoft (R) Build Engine version 12.0.31101.0", failiing builds with new C# 6 syntax :(
Support Staff 3 Posted by Feodor Fitsner on 21 Jul, 2015 04:05 PM
Add this to
installorbefore_buildsection:4 Posted by Aristarkh Zagor... on 21 Jul, 2015 04:48 PM
Thanks, Feodor, your support is as great as always.
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?
Support Staff 5 Posted by Feodor Fitsner on 21 Jul, 2015 07:22 PM
Yes, add it into appveyor.yml.
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.
6 Posted by Jeremiah Gowdy on 21 Jul, 2015 07:49 PM
We would like to migrate to VS 2015 also, can you move our account?
Support Staff 7 Posted by Feodor Fitsner on 21 Jul, 2015 07:52 PM
Done. There is still RC, RTM will be available later today.
8 Posted by chris on 21 Jul, 2015 10:51 PM
please migrate me to the default 2015 image as well. thank you!
Support Staff 9 Posted by Feodor Fitsner on 22 Jul, 2015 05:08 AM
@Chris - what's account name that should be migrated?
10 Posted by chris on 22 Jul, 2015 01:48 PM
@Feodor my account name is Authenticom ...thanks!
Support Staff 11 Posted by Feodor Fitsner on 22 Jul, 2015 04:48 PM
Moved.
12 Posted by chris on 22 Jul, 2015 05:50 PM
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
I've tried the default image and manually selecting the VS 2015 azure image...same results for both.
Support Staff 13 Posted by Feodor Fitsner on 22 Jul, 2015 05:51 PM
If your project build step is set to "MSBuild" make sure .sln file has
# Visual Studio 14header (not# Visual Studio 2013); otherwise AppVeyor will force MSBuild 12.0.14 Posted by Aristarkh Zagor... on 27 Jul, 2015 07:49 AM
Could the "d3-x" account be moved also?
Support Staff 15 Posted by Feodor Fitsner on 27 Jul, 2015 05:04 PM
Moved.
16 Posted by Aristarkh Zagor... on 28 Jul, 2015 08:41 AM
Thank you, Feodor!
17 Posted by James White on 28 Jul, 2015 03:12 PM
When do you expect that the VS 2015 image will be as fast to queue as the Windows Server 2012 image?
Thanks!
James
18 Posted by Michael Sherman on 28 Jul, 2015 05:15 PM
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?
Thanks!
Support Staff 19 Posted by Feodor Fitsner on 28 Jul, 2015 06:37 PM
VS 2015 on Pro environment will be available this week. We can move you to OSS environment for now with VS 2015 installed?
20 Posted by Jeremiah Gowdy on 28 Jul, 2015 06:42 PM
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.
Since this is a JIT issue, it should affect only the runtime of your software, not the compilation which AppVeyor provides.
Blog: http://nickcraver.com/blog/2015/07/27/why-you-should-wait-on-dotnet-46/
KB: https://support.microsoft.com/en-us/kb/3065367
POC: https://github.com/StackExchange/RyuJIT-TailCallBug
Second defect: https://github.com/dotnet/coreclr/issues/1299
Support Staff 21 Posted by Feodor Fitsner on 28 Jul, 2015 06:52 PM
There are breaking changes in BCL as well. Take this issue with Service Bus for example: http://stackoverflow.com/questions/28333034/how-do-i-report-a-bug-i...
22 Posted by msherman on 28 Jul, 2015 06:54 PM
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.
Regards,
Sherm
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:58 AM.