AppVeyor: update to Visual Studio 2017 #3606
Conversation
|
maybe we should get rid of 2012, does anyone use that. we'd still have a lot 2008/2010/2013/2015/2017 |
|
Right, holding down the amount is a good idea and presumably that single one alone rarely finds an issue for us... |
|
Just curious, why 2012 out of all versions? |
|
It's probably worth leaving in the last version that can target Windows X,
where X is XP/Vista/7/8 or whatever it is that we still claim to support.
Presumably, people who are still targeting older versions will be using the
latest SDK that still supports it.
|
|
That would be Visual Studio 2008 for Windows 2000 and Visual Studio 2017 for Windows XP and Vista. It's not possible to run the tests with Visual Studio 2008, though, so we should also keep Visual Studio 2010. |
|
From my perspective it wasn't about 2012 specifically but rather thinking through if we can reduce the number of builds without sacrificing too much functionality. |
Remove the Visual Studio 2012 and 2013 builds as they add little value. Ref: curl#3606 Closes
|
I've created #3614 to remove the 2012 and 2013 builds. If that's OK to merge, I'll rebase this one and add a commit to remove the 2015 build too. |
Anecdotal. I just haven't seen it that much. I would also like to reduce the number of builds. I did some empirical searching Visual Studio 2005 - 182,259 How about 2008, 2010, 2017, and we will eventually need to add support for 2019 due out this year. |
|
ah just saw your comment we posted at the same time. sounds good. |
Currently, we're using the default Visual Studio 2015 image for everything. Closes curl#3606
The Visual Studio 2017 image has Visual Studio 2015 and 2017 installed. Closes curl#3606
Switch all Visual Studio 2015 builds to Visual Studio 2017. It's not a moving target anymore as the last update, Update 9, has been released. Closes curl#3606
MarcelRaad
force-pushed
the
appveyor_vs2017
branch
from
994ddbc
to
7050509
Compare
MarcelRaad
changed the title
|
Merged the other two changes and rebased this one. |
The Visual Studio 2017 image has Visual Studio 2015 and 2017 installed. Closes #3606
Switch all Visual Studio 2015 builds to Visual Studio 2017. It's not a moving target anymore as the last update, Update 9, has been released. Closes #3606
Currently, we're using the default Visual Studio 2015 image for everything. Closes curl#3606
The Visual Studio 2017 image has Visual Studio 2015 and 2017 installed. Closes curl#3606
Switch all Visual Studio 2015 builds to Visual Studio 2017. It's not a moving target anymore as the last update, Update 9, has been released. Closes curl#3606
The last major update to Visual Studio 2017 has been released and is available on AppVeyor. It requires the non-default Visual Studio 2017 worker Image, which can also be used for Visual Studio 2015 and comes with more modern, but less software.