This issue started a couple of months ago when we upgraded to VS2015 (from 2013), but I was too busy reporting. Would love to have NCrunch working again in the new environment.


This is the error from the NCrunch tests window:
---
System.Exception: An exception was thrown in the remote environment: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> nCrunch.Common.UserException: Errors occurred while trying to load the project file:
API restriction: The assembly '' has already loaded from a different location. It cannot be loaded from a new location within the same appdomain.
at nCrunch.Compiler.RemoteBuildRunner.(FilePath ,   , String , String , DirectoryPath , String )
at nCrunch.Compiler.RemoteBuildRunner.AnalyseComponentBuild(FilePath projectFilePath, BuildXml buildXml, String useBuildConfiguration, String useBuildPlatform, DirectoryPath solutionDir, String solutionName, List`1 importExpressionsToEvaluate, ProcessorArchitecture buildProcessProcessorArchitecture, DirectoryPath workspaceBasePath)
--- 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.Compiler.IRemoteBuildRunner.AnalyseComponentBuild(FilePath projectFilePath, BuildXml buildXml, String useBuildConfiguration, String useBuildPlatform, DirectoryPath solutionDir, String solutionName, List`1 importExpressionsToEvaluate, ProcessorArchitecture buildProcessProcessorArchitecture, DirectoryPath workspaceBasePath)
at nCrunch.Core.BuildManagement.BuildProcessLauncher..(IRemoteBuildRunner )
at nCrunch.Core.BuildManagement.BuildProcessLauncher.(Action`1 , IBuildableProject , ExternalProcess )
at nCrunch.Core.BuildManagement.BuildProcessLauncher.(Action`1 , ProcessorArchitecture , GridClientId , IBuildableProject , IList`1 )
at nCrunch.Core.BuildManagement.BuildProcessLauncher.AnalyseComponentBuildInExternalProcess(FilePath projectFilePath, BuildXml buildXml, String useBuildConfiguration, String useBuildPlatform, DirectoryPath solutionDir, String solutionName, List`1 importExpressionsToEvaluate, ProcessorArchitecture processorArchitecture, VisualStudioVersion vsVersion, IList`1 customEnvironmentVariables)
at nCrunch.Client.ComponentLoader.SnapshotComponentFactory.(ProcessorArchitecture )
at nCrunch.Client.ComponentLoader.SnapshotComponentFactory.CreateSnapshotComponentFromXml(FilePath projectFilePath, BuildXml projectXml, FilePath solutionFilePath, String[] additionalFilesToIncludeAtSolutionLevel, Boolean isLoadedFromFile, ISnapshotConfig snapshotConfig, VisualStudioVersion vsVersion)
---

Note: This is a 100% copy/paste from the window, I did NOT remove anythin (assembly '' is really empty).

Environment:

• Windows Server 2012 R2
  
• Visual Studio 2015 Update 3
  
• NCrunch 2.25 (experience error once we upgraded to VS2015 + NCrunch 2.20. Using VS2013 + NCrunch 2.20 was working fine)
  

Do you have any idea how to fix this?
Or how to troubleshoot this to find better information about the root cause?

The VS/C# solution does build fine on VS2015 and also on our build server without Visual Studio (MSBuild + Windows SDK + .NET target pack).

Thanks

- It is specific to the solution/projects
- Even some projects in the solution build fine, but at some point one project fails and naturally all dependent projects fail from there on
- Custom coding (I assume you mean build-events or stuff like that):
* Not in the project which fails.
* There is a post-build event executing in the EXE project, which is the last to be built in the solution. It does some app.config merging, but this is skipped in NCrunch altogether.
- We do have Resharper and Reflector installed in our IDE.
- What logfile do you mean and where can it be found?

Another speciality in our solution:
- All .csproj files do have "DoNotCopyLocalIfInGac=true" to match the old behavior of VS2013. This was necessary due to a 3rd party assembly that relies on that behavior.

<PropertyGroup>
<!-- Fix the default copy local behaviour changed in VS 2015 -->
<DoNotCopyLocalIfInGac>true</DoNotCopyLocalIfInGac>
</PropertyGroup>

Also, we do reference a 3rd party ActiveX control (COM).

And we upgraded NUnit from 2.6.x to 3 at the same time when upgrading to VS2015.

I could fix it while trying to create a minimal solution which reproduces the issue.

We had this import in the failing .csproj files:


I don't really understand why, but at the moment we can live without this import.

The "exists(<path>)" was there to not import it on the build machine where this file isn't present (no VS installed).

Thanks for the workaround!