The OutputPath property is not set for project

This is quite a common error often seen when the projects within your solution can't be built independently using MSBuild.

You should in theory be able to replicate the error outside of NCrunch by building your .proj files directly using MSBuild on the command line.

Make sure each of your .proj files has a default configuration specified in a PropertyGroup, for example: <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>

You can also specify the $(Configuration) variable in the NCrunch configuration for each component (try setting 'UseBuildConfiguration' to DEBUG), though this is a bit of a dirty way of getting around the problem.

Interesting. Do the projects build on their own outside the solution? If not - hit the Bug Report button and I'll take a look at the log file.

I'd say that this is definitely likely to cause you problems. Try adjusting this to be a path relative to the project file you're building, and see if this helps.

You may also need to use the AdditionalFilesToInclude option to make sure the imported build script is found by NCrunch and copied to the workspace. NCrunch is usually pretty good with working out these sorts of dependencies, but imported MSBuild scripts can give it trouble if you're using MSBuild variables to describe their paths.

Nice going. Try introducing the Platform property as a element of an unconditional PropertyGroup inside the build script. This will be effectively the same as injecting it through the command line, and it should work with NCrunch.

Thanks! Will take a look.

Hi Andrew,

Thanks for sending through the log file. I can reproduce this problem consistently and can confirm that NCrunch has a compatibility issue with static libraries shared between projects.

So far, NCrunch's support for C++ projects has been shallow and is quite limited. I do have some plans to extend better support in this area, although the build behaviour around C++ projects is quite different to other .NET projects and some effort will be required before I can safely warrant that NCrunch will support these projects consistently in a range of different environments.

1.31b (due for release this week) contains a fix that will allow NCrunch to find the lib file, but usage of the file by other projects within the solution is so far impossible. The best option I can provide you with would be to separate the build of your C++ projects into a different solution, then introduce direct DLL assembly references from your other projects to the build outputs from this solution. Better C++ support should be added in a future release several months from now.


Cheers,

Remco