D
Dick (English)
Guest
It is now more than a year ago that VS 2017 was released. Not long after the release I tried to install VS 2017 together with VS 2015 (which I needed for a program language which does not support above VS 2015.) This turned out to be a tiresome operation, and only with the help of a good support agent we managed to get it working, requiring lots of manual deletions of all kind of files. As I shortly after that was forced to roll back a W10 installation and lost VS 2017 in the process, I decided not to bother trying to reinstall VS 2017, especially because it was much slower than 2015, totally contrary to what was promised.
Now version 15.8 was released I decided to reinstall a Community version next to a Professional version of VS 2015 because I want to start working on a UWP program and the sample set is only working on VS 2017. Despite we are 8 decimal point version numbers higher the installation procedure is still as crappy as it was over a year ago.
In short, vs_Community.exe starts, installs some files in the %temp% directory and then stops without any message. Even a software developer with a few month experience knows that if something doesn't work as expected, (s)he should program a message indicating as good as possible why the program stops. Why isn't that done for the Visual Studio installer? It doesn't help to write "We recommend that you try the Visual Studio web installer—we think you'll find it a good experience.". Installing Visual Studio is in fact the worst experience one can get.
Most of the 100's of installation problem posts I can find (I am of course not the only one suffering from the poor working of Visual Studio) are about running InstallCleanup.exe - as there is no C:\Program Files (x86)\Microsoft Visual Studio\Installer\ directory this step won't help, or about deleting all kind of VS 2015 files and directories which I can not do.
I would have no problems to keep using VS 2015, but since the Creators update UWP program samples from Microsoft do not work anymore in VS 2015.
I do not expect that the VS team can solve the installation problem. As nothing has changed in over a year, it won't change the next years either and I can probably only install a future VS version if I have no prior VS version and a new Pc, I guess. My main question is how & why the use of VS2015 is not possible for new UWP samples. If that can be circumvented I don't need to bother for VS 2017 for the next year(s).
Continue reading...
Now version 15.8 was released I decided to reinstall a Community version next to a Professional version of VS 2015 because I want to start working on a UWP program and the sample set is only working on VS 2017. Despite we are 8 decimal point version numbers higher the installation procedure is still as crappy as it was over a year ago.
In short, vs_Community.exe starts, installs some files in the %temp% directory and then stops without any message. Even a software developer with a few month experience knows that if something doesn't work as expected, (s)he should program a message indicating as good as possible why the program stops. Why isn't that done for the Visual Studio installer? It doesn't help to write "We recommend that you try the Visual Studio web installer—we think you'll find it a good experience.". Installing Visual Studio is in fact the worst experience one can get.
Most of the 100's of installation problem posts I can find (I am of course not the only one suffering from the poor working of Visual Studio) are about running InstallCleanup.exe - as there is no C:\Program Files (x86)\Microsoft Visual Studio\Installer\ directory this step won't help, or about deleting all kind of VS 2015 files and directories which I can not do.
I would have no problems to keep using VS 2015, but since the Creators update UWP program samples from Microsoft do not work anymore in VS 2015.
I do not expect that the VS team can solve the installation problem. As nothing has changed in over a year, it won't change the next years either and I can probably only install a future VS version if I have no prior VS version and a new Pc, I guess. My main question is how & why the use of VS2015 is not possible for new UWP samples. If that can be circumvented I don't need to bother for VS 2017 for the next year(s).
Continue reading...