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

Notification

Icon
Error

BuildShadowTask Exception
habakuk
#1 Posted : Thursday, May 26, 2011 2:16:53 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 5/26/2011(UTC)
Posts: 2
Location: Nürnberg

Thanks: 1 times
Hello,

I tried to setup NCrunch for the first time and get this exception form my test projects (The productive projects are building):

C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\TeamTest\Microsoft.TeamTest.targets (14): Unerwarteter Fehler bei der BuildShadowTask-Aufgabe.
System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei Microsoft.VisualStudio.TestTools.BuildShadowReferences.BuildShadowTask.Execute()
bei Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
bei Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask, Boolean& taskResult)

Any idea where this comes from?

I use Windows7, 64bit, German, with Visual Studio 2010 and Visual Basic. NCrunch is 1.31b

Thanks!
Stefan
Remco
#2 Posted : Thursday, May 26, 2011 10:22:46 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,974

Thanks: 929 times
Was thanked: 1256 time(s) in 1169 post(s)
Hi Stefan,

Thanks for posting!

Are you using an accessor to test under the hood of your runtime code?

http://blog.hinshelwood.com/tfs-error-msb4018-the-buildshadowtask-task-failed-unexpectedly/
habakuk
#3 Posted : Friday, May 27, 2011 9:13:46 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 5/26/2011(UTC)
Posts: 2
Location: Nürnberg

Thanks: 1 times
Hello Remco,

thanks for your answer!

I use accessors (because I need them) and if I run the tests manually everything works...
Remco
#4 Posted : Friday, May 27, 2011 7:54:15 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,974

Thanks: 929 times
Was thanked: 1256 time(s) in 1169 post(s)
Gotcha. I'll need to do a bit of research to learn how the accessors work under the hood and why they are being impacted by NCrunch's build strategy. My assumption at this stage is that I'll need to introduce a fix to resolve this properly. I'll let you know if I can identify a workaround that you can apply in 1.31b :)
1 user thanked Remco for this useful post.
habakuk on 5/29/2011(UTC)
Remco
#5 Posted : Saturday, June 4, 2011 3:28:47 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,974

Thanks: 929 times
Was thanked: 1256 time(s) in 1169 post(s)
Hi Habakuk -

I've identified and resolved the accessor build issue in the upcoming 1.32b release.

Meanwhile, you can work around this problem by using the AdditionalFilesToInclude configuration option to include your .accessor files as part of the build. The issue is that NCrunch doesn't pick these files up from your build script and therefore doesn't know they exist.

I hope this helps.


Cheers,

Remco
Remco
#6 Posted : Thursday, June 16, 2011 6:09:01 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,974

Thanks: 929 times
Was thanked: 1256 time(s) in 1169 post(s)
For anyone interested, a proper fix for this issue has now been released as part of 1.32b.
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.040 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download