Hi,

Thanks for sharing this issue.

Where I've seen this before, it's usually the result of an installation problem or something going wrong inside the IDE itself.

Would you be able to submit a bug report via the NCrunch menu? The log file in the report may yield some clues as to what is happening here.

Understanding that you've already tried reinstalling the software, I'm wondering if you could try this with making sure that ALL files in the NCrunch install directory are deleted before reinstalling. If there was a previous manual installation that was overwritten, this can cause strange install problems. Also check that windows hasn't 'blocked' any of the installed files if you've extracted them from zip.

Thanks for sending through the bug report. The exception you're experiencing is below:

System.Exception: An exception was thrown in the remote environment: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNotFoundException: Could not load file or assembly 'nCrunch.VSIntegration2015' or one of its dependencies. The system cannot find the file specified.
at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.Load(String assemblyString)
at nCrunch.Core.BuildManagement.MSBuildEngineRegistry.WithRegisteredBuildEngine(BuildEngineDescription engineDescription)
at nCrunch.Client.EngineServiceInitialiser.(Nullable`1 )
at nCrunch.Client.EngineServiceInitialiser.InitialiseServiceLocator(Nullable`1 vsVersion, FilePath solutionFilePath, Boolean isHostedInSatelliteProcess, Boolean readOnlyConfig, UIState uiState, ISupplementaryEngineInitialiser initialiser, FilePath[] assembliesResidentInIDE)
at nCrunch.Client.EngineHosting.HostedEngine.Initialise(Nullable`1 vsVersion, String engineInitialiserQualifiedTypeName, FilePath solutionFilePath, Boolean monitorExecution, Boolean readOnlyConfig, UIState uiState, FilePath[] assembliesResidentInIDE)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at nCrunch.TaskRunner.Ipc.IpcMessageProcessor.(CallMethodMessage )
at nCrunch.TaskRunner.Ipc.IpcMessageProcessor.ProcessMessageReturningResult(Byte[] data)
at nCrunch.TaskRunner.Ipc.RemoteInstance.[T](Byte[] )
at nCrunch.TaskRunner.Ipc.RemoteInstance.Invoke(IMessage msg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at nCrunch.Client.EngineHosting.IHostedEngine.Initialise(Nullable`1 vsVersion, String engineInitialiserQualifiedTypeName, FilePath solutionFilePath, Boolean monitorExecution, Boolean readOnlyConfig, UIState uiState, FilePath[] assembliesResidentInIDE)
at nCrunch.Client.EngineHosting.EngineHost.(SystemEnabledEvent )

It's interesting that NCrunch seems to think that it's running under VS2015. It infers the version of VS between 2013 and 2015 by checking the versions of assemblies that are loaded into the IDE, specifically Microsoft.VisualStudio.Shell. If NCrunch sees Microsoft.VisualStudio.Shell.14.0 loaded into your VS2013 IDE, it will think this is actually VS2015.

I'm rather alarmed that an instance of VS2013 has such a major component of VS2015 loaded. Such a situation could cause all kinds of instability in the IDE. Most likely this is being caused by a 3rd party extension. I recommend disabling/uninstalling any other extensions you have installed to see if this rectifies the issue.