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

Notification

Icon
Error

Don't start builds
peshkov
#1 Posted : Friday, June 20, 2014 6:04:24 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 6/20/2014(UTC)
Posts: 2
Location: Ukraine

I've got errors while NCrunch try build projects.
In NCrunch configuration for this project the "Build process CPU architecture" set x64. In project property "Platform target" exist only AnyCPU.

---
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 OutputPath property is not set for project 'nCrunchTemp_608688dc-b3f3-492d-ba92-77379f499ee8'. Please check to make sure that you have specified a valid combination of Configuration and Platform for this project. Configuration='Debug' Platform='x86'. You may be seeing this message because you are trying to build a project without a solution file, and have specified a non-default Configuration or Platform that doesn't exist for this project.
at nCrunch.Compiler.RemoteBuildRunner.#=qX63uC$SPXQzhP1QzWI4kpJ81krb6HIqZriVZlP67100=(FilePath #=qetMFGzpeteAOjlFQBNdZ0g==, #=qnc$AsDHNz7tFD1PPqhIDKDZ9lK$p73L5cuvPOVNLGx8= #=qAWNRYu_WkOMXS7uvVWbKFA==, String #=q9P62WmIzPg0ARbW0uGPP08X$H2gVTZkFYVScNYhxA5g=, String #=qUxPgiwzIOLryTXx6pyNyXEdvLQUNISbakEbfPPllUrc=, DirectoryPath #=qFyDTR8Nl18sHH6kA23Z0lQ==, String #=qm5ixynrRPnnBtAcCTHG9sA==)
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.#=qTzVAJZZ5P0qRSY$ID5REYPoI3$KK4Wo7z4$YSHRyXg0=(CallMethodMessage #=qstUya4R_bPDeKfn9oE4RFjs3KcStCinV6zfMjgS1nH0=)
at nCrunch.TaskRunner.Ipc.IpcMessageProcessor.ProcessMessageReturningResult(Byte[] data)
at nCrunch.TaskRunner.Ipc.RemoteInstance.#=qw8wqWg7B8FbOj6IMRVANtg==[T](Byte[] #=q1wiwaVeKaJhjohibCiLJag==)
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.#=q0TUkE9DWr$7P03sUXam5$yLRahZ5gUv3lgfVcUjxEJQ=.#=qp8V_VcUqDSo0pQ6_aoY2C1rxPfaCmlHRvSKMABS19egzgS8wo1_Ld4t1fhiSOENi(IRemoteBuildRunner #=qWEeWNp9Ly2eoYna7hWF1vH_CEXS$ZsLFW5UAAyS_7uo=)
at nCrunch.Core.BuildManagement.BuildProcessLauncher.#=q2sD_J2Mk9EzOIgPNBKmIRorfnGBGN04ujtZDYObpJz_vdsomytHRyelItvWuk0Fh(Action`1 #=qDJlycuRKabFbV7EGa1_fVw==, ProcessorArchitecture #=qyIkOSv9RfEARiYQpnim3ssFe6zF0m1qPNlcrJ9EfRZQ=, GridClientId #=qk9c3djaHcgHIUExfvTs1pg==, IBuildableProject #=qreCAbSnY$x8SYjpc5WjvUHXzdOViHZ8okqBuvwS_DaY=, CustomEnvironmentVariable[] #=qmGQwe44Ky7Bzj2bEx3BPjVulfht65oOg63QaKGdk4_M=)
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.#=qthG4iLC7r_zqHc2D5cTnjmJuRwv8EPvE9d0W2cxkEC0=(ProcessorArchitecture #=qgp2l1aKRyKraU4MMiT52klRK5PaSIdM_bb0tIaDVVnk=)
at nCrunch.Client.ComponentLoader.SnapshotComponentFactory.CreateSnapshotComponentFromXml(FilePath projectFilePath, BuildXml projectXml, FilePath solutionFilePath, String[] additionalFilesToIncludeAtSolutionLevel, Boolean isLoadedFromFile, ISnapshotConfig snapshotConfig, VisualStudioVersion vsVersion)

NCrunch: This error is commonly caused by projects that are relying on the selected build configuration provided by Visual Studio in order to set the $(Platform) and $(Configuration) MSBuild properties during a build. Unless configured otherwise, NCrunch will normally use the default $(Configuration) and $(Platform) properties that are specified in a .proj file - thus in order for your project to build with NCrunch it must be possible to build the project using command line MSBuild without needing to manually inject build properties. You will most likely need to edit your .proj file to align its default $(Configuration) and $(Platform) properties with the property groups provided in the file.

Remco
#2 Posted : Friday, June 20, 2014 12:14:22 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,144

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Hi, thanks for posting!

This is a very common problem that is always caused by misconfiguration inside the project file.

There's a very useful documentation page that explains the problem in detail and suggests how you can fix it - http://www.ncrunch.net/documentation/considerations-and-constraints_project-build-platform-and-configuration.

Note that the Build process CPU architecture only controls the processor architecture used for the MSBuild.exe process - it doesn't determine the processor architecture of the assembly being built. This is instead controlled by Use build platform.
peshkov
#3 Posted : Friday, June 20, 2014 12:30:55 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 6/20/2014(UTC)
Posts: 2
Location: Ukraine

I read this link before, but it is steal unclean for me: which file i should fix in VS 2012 solution?
Remco
#4 Posted : Friday, June 20, 2014 11:06:38 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,144

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
The file containing the problem will be the project (.proj) file that NCrunch is showing the error for.
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.045 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download