Build/Test Issues

v2.5 Load failure on project that could load fine in v2.4

Started by pbering on 7,093 views


Hi, got this load failure today after updating to v2.5,

The project in question is a normal Class Library project but with no references nor CS files at all, its used for PowerShell scripts and other stuff...

The Exception:

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:
The target "_SplitProjectReferencesByFileExistence" does not exist in the project.
at nCrunch.Compiler.RemoteBuildRunner.#=qyPBW83BT__Ouz4KTKC3wJsbaCa3gAjvp8Itid$G$h9I=(FilePath #=qxfXhRbakNn2eL7LW1qShGw==, #=qop2LoDdcjucGSlJpMvacVuAetc8mJ5tgsfnWKDB4PFI= #=qET7UHgxFG8XHaI60_G$5sQ==, String #=qPEBahAX9dnQzzfP1PZ$QZXmVyBv2nJ5NR3tjOL6s8YY=, String #=qFlyfexcaLWIXo_Ek00uxSxKeSjwe14aCnXxlH10Wx$o=, DirectoryPath #=qj9um4pFk3JrrPaLcPjwKhw==, String #=qFob94sLLWJk0tVz1jd4WuQ==)
at nCrunch.Compiler.RemoteBuildRunner.AnalyseComponentBuild(FilePath projectFilePath, BuildXml buildXml, String useBuildConfiguration, String useBuildPlatform, DirectoryPath solutionDir, String solutionName, List`1 importExpressionsToEvaluate)
--- 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.#=quSof26MvRV9iJ0yZzVRGlWERD5C264Mcfm_3ptQnIgI=(CallMethodMessage #=qmQP4tx5724lV5e5NWcxqaV$9BeRS7fMHX5dUq_mW3Zw=)
at nCrunch.TaskRunner.Ipc.IpcMessageProcessor.ProcessMessageReturningResult(Byte[] data)
at nCrunch.TaskRunner.Ipc.RemoteInstance.#=qbhHxZDSq9US_GnUQJukHmQ==[T](Byte[] #=qN2oX4fZVXvDxXh$B_1hLzA==)
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)
at nCrunch.Core.BuildManagement.BuildProcessLauncher.#=qIGeZcd8Y3quHiktQYCoqsvDAkFsZtnFJ0G_Gie5W3ZY=.#=qI4ofemCJoNseFABA$rCVj647xaunkjIhQwyQ7X5qeaB2gKVoQHGfzhZJ5xH7u00g(IRemoteBuildRunner #=q4Dnoh0CulxMPS1gaJHnjj9sbwP0BJ3XhozJ6wcobsco=)
at nCrunch.Core.BuildManagement.BuildProcessLauncher.#=qKKrZkT6V0PJP_1tCv$n$iS6e7xqz3tI5cgL4hBXx6jVZoZDQ$VGUt8GK4q9Gd41I(Action`1 #=qzjbGNSs0qF_I4$s0T0icbw==, ProcessorArchitecture #=qRBrPn1BSCfWNHUqaQyBvDwmziA_T7n32K2zLtbzzMbA=, GridClientId #=qkRPlP398aQ3goZ9dLMTDmQ==, IBuildableProject #=qWX1NsbZzag_vkkukM5tiEgKMHfItTVyGItgx$M2f7ro=, CustomEnvironmentVariable[] #=qCh9FbQxTfUpbXzMAV5RSg49y7fqC_Jk1usFES0DYJB0=)
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, CustomEnvironmentVariable[] customEnvironmentVariables)
at nCrunch.Client.ComponentLoader.SnapshotComponentFactory.#=qu0NJ0eYcB$3xRlxMLjLqLev2eupBG4zWeS69obrGynE=(ProcessorArchitecture #=qXS1f4VZGpDchaRl4TtjPqCsG1pYeBPdVQX36F93KgXg=)
at nCrunch.Client.ComponentLoader.SnapshotComponentFactory.CreateSnapshotComponentFromXml(FilePath projectFilePath, BuildXml projectXml, FilePath solutionFilePath, String[] additionalFilesToIncludeAtSolutionLevel, Boolean isLoadedFromFile, ISnapshotConfig snapshotConfig, VisualStudioVersion vsVersion)
Hi, thanks for sharing this issue.

The _SplitProjectReferencesByFileExistence is declared in the MSBuild targets usually referenced from the project file. If this project file is custom-made without using standard MSBuild references, it likely isn't supported by NCrunch.

The most appropriate action in this case I think would be to ignore the project using the ignore this project completely configuration setting. When set as ignored, NCrunch will not attempt to load the project and you won't receive any errors from it.

Cheers,

Remco
That worked :) thank you.
Welcome :)

Post a reply

Log in to reply.