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

Notification

Icon
Error

Exception logged when trying to build Fody's BasicFodyAddin solution
Ralf Koban
#1 Posted : Friday, June 20, 2014 3:00:47 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/19/2014(UTC)
Posts: 44
Location: Germany

Thanks: 4 times
Was thanked: 10 time(s) in 9 post(s)
When I tried to run the tests in the BasicFodyAddin solution, NCrunch reported an exception.

Side note: Unfortunately, "Submit NCrunch Bug Report" feature doesn't seem to work on my PC. If I click "Submit Report" then I get a message box saying that the connection failed. If I click "Save Report to File", I get an empty (0kb) file.


Steps to reproduce the exception:

1. Download the zip file at: https://github.com/Fody/...ddin/archive/master.zip
2. Open solution in VS 2013 Update 2 and rebuild it
3. Enable NCrunch (run all tests automatically in parallel)
4. The "Nuget" project cannot be built, reported exception is following:

Please note: "Das Ziel "_SplitProjectReferencesByFileExistence" ist im Projekt nicht vorhanden." can be translated to "The target ... is not contained in the project."


System.Exception: An exception was thrown in the remote environment: System.Reflection.TargetInvocationException: Ein Aufrufziel hat einen Ausnahmefehler verursacht. ---> nCrunch.Common.UserException: Errors occurred while trying to load the project file:
Das Ziel "_SplitProjectReferencesByFileExistence" ist im Projekt nicht vorhanden.
bei nCrunch.Compiler.RemoteBuildRunner.#=qX63uC$SPXQzhP1QzWI4kpJ81krb6HIqZriVZlP67100=(FilePath #=qetMFGzpeteAOjlFQBNdZ0g==, #=qnc$AsDHNz7tFD1PPqhIDKDZ9lK$p73L5cuvPOVNLGx8= #=qAWNRYu_WkOMXS7uvVWbKFA==, String #=q9P62WmIzPg0ARbW0uGPP08X$H2gVTZkFYVScNYhxA5g=, String #=qUxPgiwzIOLryTXx6pyNyXEdvLQUNISbakEbfPPllUrc=, DirectoryPath #=qFyDTR8Nl18sHH6kA23Z0lQ==, String #=qm5ixynrRPnnBtAcCTHG9sA==)
bei nCrunch.Compiler.RemoteBuildRunner.AnalyseComponentBuild(FilePath projectFilePath, BuildXml buildXml, String useBuildConfiguration, String useBuildPlatform, DirectoryPath solutionDir, String solutionName, List`1 importExpressionsToEvaluate)
--- Ende der internen Ausnahmestapelüberwachung ---
bei System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
bei System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
bei System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
bei nCrunch.TaskRunner.Ipc.IpcMessageProcessor.#=qTzVAJZZ5P0qRSY$ID5REYPoI3$KK4Wo7z4$YSHRyXg0=(CallMethodMessage #=qstUya4R_bPDeKfn9oE4RFjs3KcStCinV6zfMjgS1nH0=)
bei 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)

Remco
#2 Posted : Friday, June 20, 2014 10:59:06 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 sending through the bug report (it did actually come through), and sharing the clear steps to reproduce. This made it very easy to analyse the problem.

This particular project has been hand-coded with custom build targets. The build targets included in the project don't reference any of the standard MSBuild targets, which means that none of the conventional build steps are followed. This means that NCrunch has no way to integrate with this project's build.

It looks as though the project itself is more of a packaging/copying step rather than a set of compiled files. Are you able to get away with simply ignoring it in your NCrunch configuration? There are no files in this project that could contain code or code executed by tests.

Cheers,

Remco
1 user thanked Remco for this useful post.
Ralf Koban on 6/21/2014(UTC)
Ralf Koban
#3 Posted : Saturday, June 21, 2014 5:09:01 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/19/2014(UTC)
Posts: 44
Location: Germany

Thanks: 4 times
Was thanked: 10 time(s) in 9 post(s)
Hi Remco,

thanks for the information. I will ignore it in the NCrunch configuration.

BR
Ralf
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.043 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download