NAnt - A .NET Build Tool

Logged In: YES
user_id=707851

I've modified the <solution> task to allow matching between
assembly reference and project using assembly name if the
assembly file does not exist.

This should fix your problem (I verified it ofcourse).

Logged In: YES
user_id=103371

Well, if the assembly is built as a part of current
solutions... I would expect that the file names are matched...

But I would expect that matching to work at least when the
\bin\...
directory is replaced with
\obj\.. one (in hintpath).

I.e., if You modify the csproj file to conatin
..\Lib_General\obj\...
isntead of
..\Lib_Parent\bin\...

the solution would fail also (but it should work in this
special case at least)

Hope I was clear enough.

Logged In: YES
user_id=707851

Gert,

When no output directory is specified and the reference
cannot be resolved using assembly folders, then the hintpath
is used to determine the path of an assembly.

In your case, the reference to MyCompany.Lib_General in the
Lib_Specific project has a hintpath (..\Lib_Parent...) that
does not match the output path of the Lib_General project,
which is why we can't detect that it actually references the
Lib_General project.

Now, we could change it to match assembly and project
references on assembly name instead of file name. But I'm
not sure if this is better or worse than matching on file name.

What do you think ?

Logged In: YES
user_id=103371

Seems like I have to reopen the bug... A modified the build
file a little bit, and it fails again..
{Changed
<solution configuration="debug"
outputdir="${build.dir}/bin" >
to
<solution configuration="debug" >

in Fail2 task
}


Or maybe shoudl it be another report?

Logged In: YES
user_id=707851

This issue is now fixed in cvs.

Thanks for the report !