Failing build projects that have custom .targets files

Hi gang:

So the projects in my solution include custom .targets files, through the Import directives, like so:

<Import Project="$([MSBuild]::GetDirectoryNameOfFileAbove($(MSBuildProjectDirectory), `msbuildroot.marker`))\build\base\crosstarget.settings.targets" />

Basically this walks up my source tree looking for the marker file, (finding enlistment root), then walks up the root from there. Naturally this fails spectacularly with ncrunch, since it copies the project off into a totally separate place.

Any suggestions?

This should be very easy to fix - just make sure you include your custom target files (and their dependencies) with NCrunch using the AdditionalFilesToInclude configuration setting.

Thanks. The solution does work, however it's not terribly practical. My solution has 60 projects in it. Setting this for every project is too onerous, given that only relative paths appear to work, and they have to be adjusted for each project.

(Plus how do you migrate these settings to other devs on the team?)

Thanks!

Global settings to permit this sort of thing at solution level are on the list of things to address :) You should be able to share these settings with your team mates by ensuring the ncrunch .xml configuration files are checked into your source control system.