Please clarify which version of Visual Studio is in each "OS" choice.
First, this is a great service that is working very well. Very nice work!
I was confused about how to choose VS2013 vs VS2015. In particular, it isn't obvious that all the choices that don't mention a VS version are using VS2013 (I think). Also, it is confusing that this choice was presented as an "operating system" choice where really it is an "operating system + compiler" choice. It may be better to relabel things with more precise names.
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 31 Jul, 2015 11:39 PM
You're right, "OS" is quite outdated thing as there is always Windows Server 2012 R2. There was an idea to have multiple OSes, client and server...
Default "os" (Windows Server 2012 R2) has these VS versions depending on environment:
1) Pro environment (all paid plans and trials) - VS 2013
2) "New" OSS environment based on Hyper-V - VS 2013 and VS 2015
3) Azure environment (OSS accounts not moved to a new environment) - VS 2013
Thus if you are on Pro environment then you should choose "Visual Studio 2015" image to build on VS 2015.
I know such fragmentation is bad, but it's evolution mostly rather than revolution (.NET 4.6 which is in-place update breaks a lot of builds working fine on VS 2013). We'll be changing that over time.
2 Posted by brian on 01 Aug, 2015 05:04 AM
RE (2), there are systems that have both VS2013 and VS2015 on them? Then, how do I choose which version of Visual Studio to use for my build? Could you show an example matrix that does two separate builds: one for VS2013 and another with VS2015? Thanks!
3 Posted by brian on 01 Aug, 2015 07:31 PM
OK, I figured it out. See my appveyor.yml at https://github.com/briansmith/ring. In particular, you have to set the PATH so that VS2015's msbuild.exe is found before VS2013's msbuild.exe, as described at http://www.appveyor.com/updates.
I suggest that "Visual Studio Version" be made a separate dimension of the build matrix so that the matrix becomes Visual Studio Version x Platform x Configuration.
Support Staff 4 Posted by Feodor Fitsner on 01 Aug, 2015 07:33 PM
Right, thanks for the update!
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:58 AM.