Comment from the ANT world (big brother to NANT) ALL forward slashes \ were considered escape characters so C:\TEMP\whatever would have to specified as C:\\TEMP\\whatever
A most decidedly unrelated note Is there a way out of DLL *&ll? When the Microsoft IDE creates a DLL assembly it must ALWAYS deploy (versus just keeping it in debug or release) So far the only solution i know is to: 1)Create all subsidiary DLL's (Utilities, Comm, DBAccess) and check the DLL's into version control 2)Pull the DLL's into a special DLL folder 2)In your IDE References point the subsidiary DLL to the special DLL folder(instead of the default behavior of including in the local copy) Alternatively Is there a way to TURN OFF strong named assemblies so a .NET binary will take the first assembly DLL (regardless of Version) Thanks and have a good memorial day- Martin Gainty ----- Original Message ----- From: "Gert Driesen" <[EMAIL PROTECTED]> To: "FRANCIS, Paul" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Friday, May 28, 2004 2:12 AM Subject: Re: [Nant-users] Solution Task and Strong Names > Paul, > > This should indeed have been fixed. Can you send me a small repro for this > issue ? > > Thanks, > > Gert > ----- Original Message ----- > From: "FRANCIS, Paul" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, May 27, 2004 4:45 PM > Subject: [Nant-users] Solution Task and Strong Names > > > > Hi > > > > Looking at > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg02597.html > > > <http://www.mail-archive.com/[EMAIL PROTECTED]/msg02597.html> > > it seems the Solution task has been fixed so VBC now looks in the right > > place for SNK files. However, I've just got the latest nightly build (25 > May > > 2004) and still get the "Error creating assembly manifest: Error reading > key > > file '..\..\daab.snk' -- The system cannot find the file specified." > > message. > > > > > > I've tried the following and neither work.... > > > > <Assembly: AssemblyKeyFile("..\..\daab.snk")> > > <Assembly: AssemblyKeyFile("daab.snk")> > > > > ....but a hard-coded path does work. I'm compiling using an .SLN file like > > this: > > > > <solution solutionfile="${latestdir}\MySolution.sln" > > configuration="${typeofbuild}" outputdir="${builddir}"> > > </solution> > > > > > > Has this been released yet? > > > > Thanks. Paul. > > > > > > ...................................................................... > > BUPA > > ..................................................................... > > BUPA House, 15-19 Bloomsbury Way, London, WC1A 2BA > > ..................................................................... > > Internet communications are not secure and therefore BUPA does > > not accept legal responsibility for the contents of this message. Any > > views or opinions presented are solely those of the author and do > > not necessarily represent those of BUPA. > > ..................................................................... > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle 10g. > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > _______________________________________________ > Nant-users mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nant-users > ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
