Bugs item #1076015, was opened at 2004-11-30 16:12
Message generated for change (Comment added) made by gkello
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1076015&group_id=31650
Category: Tasks
Group: 0.85
Status: Open
Resolution: Fixed
Priority: 5
Submitted By: Gert Kello (gkello)
Assigned to: Gert Driesen (drieseng)
Summary: "solution" task and project reference parsing
Initial Comment:
I have a project, with file name like
"Lib_General.csproj". Inside the project file, the
assmbly name is overridden with AssemblyName =
"MyCompany.Lib_General"
Another project, named "Lib_Specific", has reference to
this project. But not as project reference, but as
usual reference to assembly
<Reference
Name = "MyCompany.Lib_General"
AssemblyName = "MyCompany.Lib_General"
HintPath = ".."
/>
When I try to build a solution (using <solution> task)
which includes lib_General project and Lib_Specific
project, whene compiling the lib_specific, nant
complains about not beeing able to find referenced
assembly "MyCompany.Lib_General" (and the build order
is wrong).
----------------------------------------------------------------------
>Comment By: Gert Kello (gkello)
Date: 2004-12-30 18:56
Message:
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.
----------------------------------------------------------------------
Comment By: Gert Driesen (drieseng)
Date: 2004-12-30 18:35
Message:
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 ?
----------------------------------------------------------------------
Comment By: Gert Kello (gkello)
Date: 2004-12-30 15:29
Message:
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?
----------------------------------------------------------------------
Comment By: Gert Driesen (drieseng)
Date: 2004-12-11 09:36
Message:
Logged In: YES
user_id=707851
This issue is now fixed in cvs.
Thanks for the report !
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1076015&group_id=31650
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
nant-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nant-developers
