Build error using reference path

After changing the Project-references from absolute references to reference paths my projects do not build in NCrunch. The MSBuild Works well, so the VS solution does. The error Message is "Der Typ oder Namespace log4net konnte nicht gefunden werden.." ("The Type or Namespace log4net could not be found...). The tests run perfectly with Visual Studio testrunner and ReSharper. Is there an issue with using VS's Reference Path?

Thanks in advance for any suggestions.
Jürgen.

(Windows7 64Bit, VS2008, NET3.5, NCrunch 1.43)

Hi, thanks for posting!

Can you tell me a bit more about the VS Reference Path you are using? Is this represented as a normal <ProjectReference> tag inside the build XML? Or is it some other mechanism? Can you show me the build XML that is placed in your project file representing the reference?


Cheers,

Remco

Hi,
it seems, that the order of searching for referenced assemblies differs from what MSBuild does:

" The default search order is
■ Files from the current project – indicated by {CandidateAssemblyFiles}.
■$(ReferencePath) property that comes from .user/targets file.
■$(HintPath) indicated by reference item.
■Target framework directory.
... "

Probably the $(ReferencePath) (coming from the csproj.user file) is ignored?

The problem occured after re-arranging commonly used DLL's (from scattered local dir's to an 'assemblies' folder that is used by all projects) and using the "Reference Path" to redirect to this folder w/o setting all references (about 100 projects, hundreds of references) manually.

Setting the ReferencePath in the VS IDE results in an user file (*.csproj.user) like this:
<Project xmlns="(- BROKEN LINK -)">
<PropertyGroup>
<ReferencePath>D:\Projekte\Assemblies\bia\;D:\Projekte\Assemblies\ext\</ReferencePath>
</PropertyGroup>
</Project>


Best regards from germany,
Juergen

Hi Juergen,

Thanks for the in-depth analysis. I've managed to reproduce this problem locally. It looks as though NCrunch isn't picking up the reference paths during its analysis of the project at load time. I'll see what I can do about getting this issue fixed in the next minor release.


Cheers,

Remco

Hi,
when can we expect the next release solving this issue. At the moment the program is more or less useless for us.

Regards,
Juergen

Hi Juergen -

The next release is still a few weeks away. If you like, I can follow up with you directly as soon as I have a test build available with a solution to the above problem?


Cheers,

Remco

For anyone interested, support for custom configured assembly reference paths has been introduced with the newly released version of NCrunch (v1.45).