Hi,

The problem you've referenced (GH-8073) is present for all versions of Visual Studio, unfortunately. The PR behind this issue was submitted to a component within the ASP.NET MVC project space to address a very specific compatibility issue with that component. Basically, it's a new part of ASP.NET that was designed in such a way as to make NCrunch support completely impossible without a code change. This change has now been accepted and my understanding is that it will be released with .NET Core 2.2.

So in short, if you're not hit with this problem now, upgrading won't change anything.

VS15.8 does have a known compatibility issue with NCrunch when working with classic .NET Framework 4.6.1 projects that make use of certain package dependency arrangements. Most people probably won't be affected by it, but there are early builds of NCrunch v3.19 that have been posted here in the forum to address it.

v3.19 will be released very soon. Probably tonight actually.

If you want to ensure stability in your environment, I recommend following either N-1 for each version of VS you use, or at least waiting 2-3 weeks after the release of a new version for the eco-system to catch up before you upgrade.