Hi, thanks for sharing this problem.

Can you confirm if running the devenv.exe /setup step as an administrator made any difference here?

If not, does running "devenv.exe /rootsuffix test" suppress the problem? (note this will temporarily run VS with a different settings root).

devenv.exe /rootsuffix opens up a new instance of VS then it closes. I may have briefly noticed a stacktrace the first time.

Changing the rootsuffix for VS basically changes the root registry key that VS uses to store its settings. When used like this, it's a blunt way of pulling VS through a full configuration reset, since the requested root doesn't exist and will therefore be populated with defaults. If VS explodes while attempting to this, I would say there is something seriously wrong with your VS installation or there may be other software on your machine interfering with its normal operation.

I was hoping to use the above step to identify whether the problem is related to your VS configuration/state or something more specific with NCrunch. Unfortunately now we're only left with more questions.

The bug report you sent through indicates NCrunch is failing to load extremely early in the process. This is prior to any logs being reliably captured. Since you've already uninstalled and reinstalled NCrunch a few times over, I think we can safely assume it's not related to NCrunch's install state. This means we have the following suspects:
- VS itself is corrupt and malfunctioning (I think this is highly likely considering the catalyst was installation of pre-release software)
- Other software interfering with normal operation of VS/NCrunch (i.e. virus scanner, O/S level security/permissions issues, etc)
- Other software relied on by VS/NCrunch is in an inconsistent or malfunctioning state (i.e. .NET framework, O/S, MSBuild, etc)

A full uninstall and reinstall of VS may fix this but I have no way to confirm 100% that it will.

Another way we can further analyse the problem would be to start VS with a debugger attached to it and see what blows up. VS usually has a few internal exceptions that are raised during its normal operation, but since this is happening on NCrunch initialisation, I'd be particularly interested in any exceptions with a stack trace containing an NCrunch namespace. Since we're not getting any trace data from NCrunch itself, an early exception is highly likely.

How would I do that?

List of exceptions related to ncrunch or not related to another extension (ie. github) thrown during startup:

Managed Debugging Assistant 'LoadFromContext' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'LoadFromContext' :** 'The assembly named 'nCrunch.VSIntegration2017' was loaded from 'file:///C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/Common7/IDE/Extensions/Remco Software/NCrunch for Visual Studio 2017/nCrunch.VSIntegration2017.dll' using the LoadFrom context. The use of this context can result in unexpected behavior for serialization, casting and dependency resolution. In almost all cases, it is recommended that the LoadFrom context be avoided. This can be done by installing assemblies in the Global Assembly Cache or in the ApplicationBase directory and using Assembly.Load when explicitly loading assemblies.'

--

Managed Debugging Assistant 'LoadFromContext' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'LoadFromContext' :** 'The assembly named 'nCrunch.VSAddIn' was loaded from 'file:///C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/Common7/IDE/Extensions/Remco Software/NCrunch for Visual Studio 2017/nCrunch.VSAddIn.DLL' using the LoadFrom context. The use of this context can result in unexpected behavior for serialization, casting and dependency resolution. In almost all cases, it is recommended that the LoadFrom context be avoided. This can be done by installing assemblies in the Global Assembly Cache or in the ApplicationBase directory and using Assembly.Load when explicitly loading assemblies.'

--

Managed Debugging Assistant 'LoadFromContext' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'LoadFromContext' :** 'The assembly named 'nCrunch.Common' was loaded from 'file:///C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/Common7/IDE/Extensions/Remco Software/NCrunch for Visual Studio 2017/nCrunch.Common.DLL' using the LoadFrom context. The use of this context can result in unexpected behavior for serialization, casting and dependency resolution. In almost all cases, it is recommended that the LoadFrom context be avoided. This can be done by installing assemblies in the Global Assembly Cache or in the ApplicationBase directory and using Assembly.Load when explicitly loading assemblies.'


--

Managed Debugging Assistant 'LoadFromContext' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'LoadFromContext' :** 'The assembly named 'nCrunch.Compiler' was loaded from 'file:///C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/Common7/IDE/Extensions/Remco Software/NCrunch for Visual Studio 2017/nCrunch.Compiler.DLL' using the LoadFrom context. The use of this context can result in unexpected behavior for serialization, casting and dependency resolution. In almost all cases, it is recommended that the LoadFrom context be avoided. This can be done by installing assemblies in the Global Assembly Cache or in the ApplicationBase directory and using Assembly.Load when explicitly loading assemblies.'

--

Managed Debugging Assistant 'LoadFromContext' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'LoadFromContext' :** 'The assembly named 'AWSSDK' was loaded from 'file:///C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/Common7/IDE/Extensions/Remco Software/NCrunch for Visual Studio 2017/AWSSDK.DLL' using the LoadFrom context. The use of this context can result in unexpected behavior for serialization, casting and dependency resolution. In almost all cases, it is recommended that the LoadFrom context be avoided. This can be done by installing assemblies in the Global Assembly Cache or in the ApplicationBase directory and using Assembly.Load when explicitly loading assemblies.'

--

Managed Debugging Assistant 'LoadFromContext' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'LoadFromContext' :** 'The assembly named 'Ionic.Zip' was loaded from 'file:///C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/Common7/IDE/Extensions/Remco Software/NCrunch for Visual Studio 2017/Ionic.Zip.DLL' using the LoadFrom context. The use of this context can result in unexpected behavior for serialization, casting and dependency resolution. In almost all cases, it is recommended that the LoadFrom context be avoided. This can be done by installing assemblies in the Global Assembly Cache or in the ApplicationBase directory and using Assembly.Load when explicitly loading assemblies.'

--

Managed Debugging Assistant 'LoadFromContext' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'LoadFromContext' :** 'The assembly named 'nCrunch.WpfUI' was loaded from 'file:///C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/Common7/IDE/Extensions/Remco Software/NCrunch for Visual Studio 2017/nCrunch.WpfUI.DLL' using the LoadFrom context. The use of this context can result in unexpected behavior for serialization, casting and dependency resolution. In almost all cases, it is recommended that the LoadFrom context be avoided. This can be done by installing assemblies in the Global Assembly Cache or in the ApplicationBase directory and using Assembly.Load when explicitly loading assemblies.'

--

Managed Debugging Assistant 'LoadFromContext' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'LoadFromContext' :** 'The assembly named 'nCrunch.Client' was loaded from 'file:///C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/Common7/IDE/Extensions/Remco Software/NCrunch for Visual Studio 2017/nCrunch.Client.DLL' using the LoadFrom context. The use of this context can result in unexpected behavior for serialization, casting and dependency resolution. In almost all cases, it is recommended that the LoadFrom context be avoided. This can be done by installing assemblies in the Global Assembly Cache or in the ApplicationBase directory and using Assembly.Load when explicitly loading assemblies.'


--

Managed Debugging Assistant 'LoadFromContext' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'LoadFromContext' :** 'The assembly named 'nCrunch.Core' was loaded from 'file:///C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/Common7/IDE/Extensions/Remco Software/NCrunch for Visual Studio 2017/nCrunch.Core.DLL' using the LoadFrom context. The use of this context can result in unexpected behavior for serialization, casting and dependency resolution. In almost all cases, it is recommended that the LoadFrom context be avoided. This can be done by installing assemblies in the Global Assembly Cache or in the ApplicationBase directory and using Assembly.Load when explicitly loading assemblies.'

--

Managed Debugging Assistant 'LoadFromContext' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'LoadFromContext' :** 'The assembly named 'RM.Product.Model.Client' was loaded from 'file:///C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/Common7/IDE/Extensions/Remco Software/NCrunch for Visual Studio 2017/RM.Product.Model.Client.DLL' using the LoadFrom context. The use of this context can result in unexpected behavior for serialization, casting and dependency resolution. In almost all cases, it is recommended that the LoadFrom context be avoided. This can be done by installing assemblies in the Global Assembly Cache or in the ApplicationBase directory and using Assembly.Load when explicitly loading assemblies.'


--

Managed Debugging Assistant 'LoadFromContext' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'LoadFromContext' :** 'The assembly named 'nCrunch.TestExecution' was loaded from 'file:///C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/Common7/IDE/Extensions/Remco Software/NCrunch for Visual Studio 2017/nCrunch.TestExecution.DLL' using the LoadFrom context. The use of this context can result in unexpected behavior for serialization, casting and dependency resolution. In almost all cases, it is recommended that the LoadFrom context be avoided. This can be done by installing assemblies in the Global Assembly Cache or in the ApplicationBase directory and using Assembly.Load when explicitly loading assemblies.'

--

Managed Debugging Assistant 'LoadFromContext' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'LoadFromContext' :** 'The assembly named 'Gallio' was loaded from 'file:///C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/Common7/IDE/Extensions/Remco Software/NCrunch for Visual Studio 2017/Modules/Gallio/Gallio.DLL' using the LoadFrom context. The use of this context can result in unexpected behavior for serialization, casting and dependency resolution. In almost all cases, it is recommended that the LoadFrom context be avoided. This can be done by installing assemblies in the Global Assembly Cache or in the ApplicationBase directory and using Assembly.Load when explicitly loading assemblies.'


--

Managed Debugging Assistant 'LoadFromContext' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'LoadFromContext' :** 'The assembly named 'nunit.core.interfaces' was loaded from 'file:///C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/Common7/IDE/Extensions/Remco Software/NCrunch for Visual Studio 2017/Modules/NUnit/nunit.core.interfaces.DLL' using the LoadFrom context. The use of this context can result in unexpected behavior for serialization, casting and dependency resolution. In almost all cases, it is recommended that the LoadFrom context be avoided. This can be done by installing assemblies in the Global Assembly Cache or in the ApplicationBase directory and using Assembly.Load when explicitly loading assemblies.'


--

Managed Debugging Assistant 'LoadFromContext' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'LoadFromContext' :** 'The assembly named 'xunit.abstractions' was loaded from 'file:///C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/Common7/IDE/Extensions/Remco Software/NCrunch for Visual Studio 2017/Modules/XUnit2/xunit.abstractions.DLL' using the LoadFrom context. The use of this context can result in unexpected behavior for serialization, casting and dependency resolution. In almost all cases, it is recommended that the LoadFrom context be avoided. This can be done by installing assemblies in the Global Assembly Cache or in the ApplicationBase directory and using Assembly.Load when explicitly loading assemblies.'

--

Managed Debugging Assistant 'LoadFromContext' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'LoadFromContext' :** 'The assembly named 'EasyHook' was loaded from 'file:///C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/Common7/IDE/Extensions/Remco Software/NCrunch for Visual Studio 2017/EasyHook.DLL' using the LoadFrom context. The use of this context can result in unexpected behavior for serialization, casting and dependency resolution. In almost all cases, it is recommended that the LoadFrom context be avoided. This can be done by installing assemblies in the Global Assembly Cache or in the ApplicationBase directory and using Assembly.Load when explicitly loading assemblies.'

--

Managed Debugging Assistant 'DangerousThreadingAPI' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'DangerousThreadingAPI' :** 'User code has attempted to call the following API: 'System.Threading.Thread.Suspend'. This may result in a deadlock in the process.'

--

Managed Debugging Assistant 'BindingFailure' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'BindingFailure' :** 'The assembly with display name 'Microsoft.VisualStudio.ExtensionEngine.XmlSerializers' failed to load in the 'LoadFrom' binding context of the AppDomain with ID 1. The cause of the failure was: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.ExtensionEngine.XmlSerializers, Version=15.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.'

--

Managed Debugging Assistant 'BindingFailure' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'BindingFailure' :** 'The assembly with display name 'PresentationUI.Aero2' failed to load in the 'LoadFrom' binding context of the AppDomain with ID 1. The cause of the failure was: System.IO.FileNotFoundException: Could not load file or assembly 'PresentationUI.Aero2, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.'


--

Thrown after opening my .sln

--

Managed Debugging Assistant 'LoadFromContext' occurred
HResult=0x00000000
Message=**Managed Debugging Assistant 'LoadFromContext' :** 'The assembly named 'nCrunch.TaskRunner' was loaded from 'file:///C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/Common7/IDE/Extensions/Remco Software/NCrunch for Visual Studio 2017/nCrunch.TaskRunner.DLL' using the LoadFrom context. The use of this context can result in unexpected behavior for serialization, casting and dependency resolution. In almost all cases, it is recommended that the LoadFrom context be avoided. This can be done by installing assemblies in the Global Assembly Cache or in the ApplicationBase directory and using Assembly.Load when explicitly loading assemblies.'

--

I've been running through the initialisation code to try and get a better understanding of this problem. Since you were at least able to submit a bug report, it appears as though at least part of NCrunch is initialised. I'm wondering if we could try a reset of NCrunch's global configuration file.

Could you try deleting or renaming the file at C:\Users\[USER]\AppData\Roaming\NCrunch\globalconfig.crunch.xml to see if this makes any difference?

Yikes! Ok, I'm glad we found this, but I'm not so happy about that experience.

Firstly, the config file shouldn't get corrupted in a way that would prevent NCrunch from loading.

Secondly, if it were corrupted, NCrunch should fall back with a sensible error and let you fix your config.

I probably should have considered this earlier, but is there any chance you still have a copy of the corrupt file? Analysing this may help me to understand what went wrong.

Perfect, thanks!!!

I suspect this works because changing configuration causes NCrunch to rewrite the corrupt config file.

Thanks for sharing your solution to this. Unfortunately I still haven't found a way to reproduce this (the corrupt config file shared above seemed to be OK on my system), so I'm keen to hear more from anyone else that gets hit by it.