Nicklas, Can you submit a bug report for this issue here : http://sourceforge.net/tracker/?atid=402868&group_id=31650&func=browse, and attach a full repro to the bug report ?
Thanks, Gert ----- Original Message ----- From: "Nicklas Norling" <[EMAIL PROTECTED]> To: "Nant-Developers (E-mail)" <[EMAIL PROTECTED]> Sent: Monday, March 22, 2004 11:59 AM Subject: [nant-dev] Possible reference problem > Hi all. > > Since 0.84 is so stabile and nice I haven't really take my time to try out > all the new good work for the solution task, until today. > > I must say it's a very impressive work. The solution task is now FAST. > A lot faster then the old was. > > Howevery, I did find a wierd thing with the references, maybe a bug, I > don't know. > > I have this rather large solution with a number of projects included that > compiles fine under 0.84. But under 0.85 nightly 20040320 I get: > > [solution] Building > 'Ifs.Fnd.Windows.Forms.Command' [Debug]... > > BUILD FAILED > > Couldn't find referenced assembly > 'Ifs.Fnd.Windows.Forms.Interfa > ces.dll'. > > after som compiling. > Looking at the csproj file in question I can see it is using a file > reference: > <Reference > Name = "Ifs.Fnd.Windows.Forms.Interfaces" > AssemblyName = "Ifs.Fnd.Windows.Forms.Interfaces" > HintPath = > "..\..\..\..\..\DeployFiles\Ifs.Fnd.Windows.Forms.Interfaces.dll" > /> > > When I CD to the directory where the csproj file is and do a dir on that > path > I get a list of that file, it is indeed compiled and deployed in that folder > as it should. > Nevertheless the HintPath doesn't appear to be working here as it did in > 0.84. > > If I re-run the compilation without first cleaning, it will not complain > about the missing > assembly. The rest of my code compiles without any problems. > > Cleaning everything up I retest this using the same solution file and > configuration but > this time running VS.NET 2003. It compiles everything without complaints. > > It appears there is a descrepacy between VS.NET 2003 and Nant 0.85 in this > respect. > > The project in question really shouldn't use file references in this case > since the assembly > it referes to is build into the same project. But as luck has it, it is > compiled before and is > available for file reference. > > /Nicke > > ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers