Support for downgrade to the recent releases
This suggestion is migrated to Developer Community. Please use below link to view the current status.
With the regular releases of VS, we sometimes get an update that breaks some of the functionalities and until the new release comes it becomes unusable. I have had this issue with 15.1 to 15.2 and now with 15.3.1 to 15.3.2, It would be more encouraging to get the updates if there is a way to a revert to previous working version (or recent releases). I would like to keep using the latest releases, but not being able to develop for a while is affecting my decision.
Michael Konecny commented
This is really annoying!! I've already spent 2 days of work trying to get my environment back up, because I accidentally updated VS and it doesn't work with my version of Intel Compiler, which I cannot update for different reasons.
Why can't you just publish an installer for every release???
Tobiasz Tomczyk commented
Recently (with 15.8 update) Microsoft.Build API was broken and my application stopped working if users installed 15.8. For corporate users, it is not acceptable to uninstall, cleanup and then install some earlier version as it should be done on multiple machines. Also, there is something bad about Microsoft versioning policy...
See this page for a manual procedure: https://docs.microsoft.com/en-us/visualstudio/productinfo/installing-an-earlier-release-of-vs2017
Same here. 15.7.1 broke our build process (nuget restore stopped working), so we ended up having to downgrade. Not an easy process.
Evgeny Morozov commented
This is a serious problem that many people are running into. Just Google (oh, sorry, Bing) for "downgrade visual studio" and see for yourself.
Also reported on Developer Community: https://developercommunity.visualstudio.com/content/problem/218991/its-really-hard-to-downgrade-install-a-specific-ve.html
Kevin Seitz commented
Same here. I was quite happy with 15.1 and 15.2 but 15.3 is a performance nightmare.
Luboš Hemala commented
I definitely support this, I have this problem since 15.3.1 and downgrading would help me a lot.