3 ms·
Yeah... good luck taking a newer version of Python an compiling it on Visual Studio 2012. I had to jump through hoops even to get 2.7 to compile and wound up a
by ericfrederich 9y ago
Yeah... good luck taking a newer version of Python an compiling it on Visual Studio 2012. I had to jump through hoops even to get 2.7 to compile and wound up abandoning it because it caused problems down the line with ctypes.
- pjmlp 9y agoVS2012 is quite pre-historic, we already had 2013, 2015 (with three updates) and are now on the third 2017 update. C99 support was added in VS2015 to the extent required by C++14, similarly C11 support was added in 2017 to the extent required by C++17.
- dragonwriter 9y ago> VS2012 is quite pre-historic You don't work in the enterprise domain which is VS’s core market, do you?
- jdmichal 9y agoStill on Visual Studio 2010 here... The pain is that everyone has to move at once due to the way the project files are upgraded when you open them in a newer version.
- T-hawk 9y agoMicrosoft fixed this after 2010. VS 2012 and onwards can open a 2010 project file with no changes. A mixed population of Visual Studios from 2010+ can work on the same project file.
- jdmichal 9y agoThat is actually extremely good to know. Thanks for the information!
- krallja 9y agoYou work around this by installing two versions of Visual Studio side-by-side.
- pjmlp 9y agoI do. We migrated to VS 2015 this year. Usually it takes one year to upgrade to a new version, after its release. We are already playing with 2017 for next year upgrade cycle.