solve the wrong CodePudding user response:
Developed on Windows platform vs2015 Cross-platform vscode CodePudding user response:
VS2019 CodePudding user response:
Vs2019 from 08,10,15,17, up to now, CodePudding user response:
2019 card is not good advice VS2017 using CodePudding user response:
Vs2017, use the most people, slowly vs2019 up CodePudding user response:
Vs 2017 and vs 2012 CodePudding user response:
vs2019 CodePudding user response:
Vs2015, development for ten years, amateur CodePudding user response:
VS 2015 CodePudding user response:
Use vccode either 12 or 15, the three more CodePudding user response:
Played a few days vs 2015. Pack once in 2017, the feeling is too slow, CodePudding user response:
2019 community, not bad CodePudding user response:
Small and exquisite VS2008 CodePudding user response:
vs2013 CodePudding user response:
2017, the feeling is good CodePudding user response:
The need to make sure that the development of techniques to determine the project: 1, if you want to use some new technology, can be used to advocate VS2017 2, if it is some old project maintenance, VS2008 - VS2010, you can CodePudding user response:
New projects are mostly in 2019 to develop.net core, maintain old projects or extension with 2015 or 2008201 0 discharge by me CodePudding user response:
vs2017 CodePudding user response:
The teacher suggested that vs2017