Hi Ali,

Thanks for posting!

Is this build step needed in order for your tests to be run? An option may be to suppress it with an override if it isn't.

I would suggest taking a look at the contents of the workspace NCrunch has created to build the project. Right click on the failed project in your Tests Window, then choose Advanced->Browse to workspace. Take a look at this workspace - it should be a near exact copy of the project as it exists in your foreground solution. Most importantly, the files needed for this particular build step will need to exist in the workspace in their expected paths. Does everything look OK to you? If there is a file missing, you may need to include it manually using the 'Additional files to include' configuration setting.

Quick update, your suggestion for excluding that build target worked great. Thanks again.

Hi, thanks for posting!

When NCrunch executes a build, it sets a property '$(NCrunch)' equal to '1'.

It's possible to use this property to change the behaviour of your build. In this case, I'd expect we'll want to use it to disable a build import. I haven't seen your project file so I'm not sure exactly how this package is hooked into it, but most likely you'll find something like:

<Import Project="..\packages\Microsoft.ServiceFabric.Actors.2.1.150\build\Microsoft.ServiceFabric.Actors.targets" />

You can disable this import for NCrunch builds as such:

<Import Project="..\packages\Microsoft.ServiceFabric.Actors.2.1.150\build\Microsoft.ServiceFabric.Actors.targets" Condition="'$(NCrunch)' != '1'" />

You can also use the condition on properties and other build steps.