Martin,
I can't see where the bug here would be. The behaviour of NAnt matches that of VS.NET.
I'm really not convinced that this is something we should support, but ... I've "fixed" it for you anyway ...
You owe me one ;-)
Gert
----- Original Message ----- From: "Martin Aliger" <[EMAIL PROTECTED]>
To: "'! nant'" <[EMAIL PROTECTED]>
Sent: Monday, October 04, 2004 12:28 PM
Subject: [nant-dev] bug: <solution> and references
Hi all,
I just found one bug (maybe regresion) that blocks mine upgrate to newest NAnt :-(
I use this (ugly looking) construct: <solution configuration="Release" outputdir="${output.dir}" includevsfolders="false"> <projects> <include name="${build.dir}/*.csproj"/> </projects> <assemblyfolders> <include name="${output.dir}"/> ... </assemblyfolders> ...
There are just two projects: A and B. B is dependant on A (via assembly reference with non-existant HintPath)
Up to now this worked well so it have to broke in those months I was away. Today it throws 'Couldn't find referenced assembly'.
Problem is that references are resolved when solution is loaded (two .csprojs in mine case) but in that time not all references are in place. Project A compiles sucessfuly but not B. References for project B are already resolved as non-existent relative path and build fails.
Please, could you look into this problem? If some patching will be needed I'm willing to do any coding around this. Martin
PS: attached is small repro (with projects A and B) [rename it to .zip]
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
