BuildShadowTask Exception

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

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/

Hello Remco,

thanks for your answer!

I use accessors (because I need them) and if I run the tests manually everything works...

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 :)

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

For anyone interested, a proper fix for this issue has now been released as part of 1.32b.