Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

[Fixed] Ncrunch can no longer build a project but VS2017 can
sadral
#1 Posted : Tuesday, February 6, 2018 12:32:53 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 2/6/2018(UTC)
Posts: 2
Location: Switzerland

Was thanked: 1 time(s) in 1 post(s)
Hello,

It seems ncrunch can no longer build one of my projects.
The solution seems to build fine in VS2017 on my machine and on the TeamCity machine.
So I don't think there are any broken references as the exception seems to suggest.

Ncrunch reports this exception while loading the project :
Quote:
System.Exception: An exception was thrown in the remote environment: System.Reflection.TargetInvocationException: Une exception a été levée par la cible d'un appel. ---> nCrunch.Common.UserException: Errors occurred while trying to load the project file:
Could not resolve COM reference "eab22ac0-30c1-11cf-a7eb-0000c05bae0b" version 1.1. Une exception a été levée par l'initialiseur de type pour 'Microsoft.Build.Collections.MSBuildNameIgnoreCaseComparer'.
à nCrunch.Compiler.RemoteBuildRunner.(FilePath , LoadTimeQuery , String , String , DirectoryPath , String , String )
à nCrunch.Compiler.RemoteBuildRunner.AnalyseComponentBuild(ComponentLoadParameters parameters)
--- Fin de la trace de la pile d'exception interne ---
à System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
à System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
à System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
à nCrunch.TaskRunner.Ipc.IpcMessageProcessor.(CallMethodMessage )
à nCrunch.TaskRunner.Ipc.IpcMessageProcessor.ProcessMessageReturningResult(Byte[] data)
à nCrunch.TaskRunner.Ipc.RemoteInstance.(Byte[] )
à nCrunch.TaskRunner.Ipc.RemoteInstance.Invoke(IMessage msg)
à System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
à nCrunch.Compiler.IRemoteBuildRunner.AnalyseComponentBuild(ComponentLoadParameters parameters)
à nCrunch.Core.BuildManagement.BuildProcessLauncher..(IRemoteBuildRunner )
à nCrunch.Core.BuildManagement.BuildProcessLauncher.(Action`1 , FilePath , String , ExternalProcess )
à nCrunch.Core.BuildManagement.BuildProcessLauncher.(Action`1 , ProcessorArchitecture , GridClientId , BuildSystemParameters , IList`1 )
à nCrunch.Core.BuildManagement.BuildProcessLauncher.AnalyseComponentBuildInExternalProcess(ComponentLoadParameters parameters, IList`1 customEnvironmentVariables)
à nCrunch.Client.ComponentLoader.SnapshotComponentLoader.(ProcessorArchitecture , String )
à nCrunch.Client.ComponentLoader.SnapshotComponentLoader.CreateComponentFromXml(FilePath projectFilePath, ParsedBuildXml projectXml, FilePath solutionFilePath, String[] additionalFilesToIncludeAtSolutionLevel, Boolean isLoadedFromFile, VisualStudioVersion vsVersion, ComponentUniqueName componentName, TaskSettings componentTaskSettings, Exception parseException, String targetFramework)


I'm not sure if it's related to the last update of VS2017 (the problem seems to have appeared after the update).
The version of VS2017 is v15.5.6.
Ncrunch version is 3.11.0.9.

Does someone have any idea of what may be causing this issue ?

Thanks.
Remco
#2 Posted : Tuesday, February 6, 2018 10:16:59 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 5,374

Thanks: 705 times
Was thanked: 878 time(s) in 835 post(s)
Hi, thanks for sharing this problem.

Can you confirm if this problem appears on the latest version of NCrunch (v3.12)? v3.12 saw quite a few fixes over v3.11 in terms of compatibility improvements for newer releases of VS.
sadral
#3 Posted : Wednesday, February 7, 2018 8:04:36 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 2/6/2018(UTC)
Posts: 2
Location: Switzerland

Was thanked: 1 time(s) in 1 post(s)
Damn, I was persuaded I already had the last version when I saw it's date.
I didn't check the actual version number ...

After installing the latest version everything works fine.

Thank you.
1 user thanked sadral for this useful post.
Remco on 2/7/2018(UTC)
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.041 seconds.