21

Updating VS to 2017.3 broke xunit test discovery for me. Everything worked fine with 2017.2 so im looking for a way to downgrade.

Alexander Herold
  • 1,057
  • 2
  • 9
  • 20
  • Broke Typescript debugging for me. I also spent an hour yesterday looking for a way to downgrade. All the (web) installer links I can find will reinstall the latest 2017.3 version. Very frustrating – PaulG Aug 17 '17 at 10:38
  • @PaulG check out my answer posted below. Forgot to answer it yesterday. – Alexander Herold Aug 17 '17 at 12:07
  • Try deleting the contents of %TEMP%\VisualStudioTestExplorerExtensions to fix your xUnit issue. – Foole Aug 18 '17 at 04:50
  • I would love to do this also, but sadly M$ doesn't want us to do it. 2017.3 is the worse upgrade for me. They managed to break even Ctrl-F7 to compile a file... 2017.3.1 seems to fix at least that. With this new update policy, the best strategy is to update when you see 2017.x.5 IMO... – jj99 Aug 22 '17 at 21:46
  • 1
    Got the same thing. How on earth is crap like this released? – sebrock Aug 28 '17 at 14:41

3 Answers3

1

A direct downgrade is not possible, but a specific version can be installed.

  1. Uninstall Visual Studio 2017 using the Visual Studio Installer.

  2. Download the Visual Studio 2017 version 15.0 RTW installer from https://my.visualstudio.com. For more information on how to do this, refer to the older downloads page

  3. Run the installer to install Visual Studio 2017, version 15.0.

found here: https://developer.xamarin.com/guides/cross-platform/windows/visual-studio/downgrading-vs-2017/

Alexander Herold
  • 1,057
  • 2
  • 9
  • 20
0

this page has instructions on how to install a specific version of VS 2017, but there is only a limited list of versions available:

https://learn.microsoft.com/en-us/visualstudio/productinfo/installing-an-earlier-release-of-vs2017

more urgent jest
  • 362
  • 4
  • 11
-1

IMO, the only real way to achieve this is after an update to make an ISO, or just download and cache the installation like described for example here:

https://learn.microsoft.com/en-us/visualstudio/install/install-vs-inconsistent-quality-network

Then if the build was actually good, uninstall the new broken one and install again from the cache. I have not tried this yet, but after this totally broken 2017.3, I would definitely start caching working installation to have something to fall back.

jj99
  • 300
  • 1
  • 11