I haven't experienced any more problems with NAnt, but I have found new
information regarding this behavior.  It appears that the path to the
key file is relative to the working folder for Visual Studio.  Hence,
you can cause VS2003 to fail/succeed at building a solution by simply
creating a shortcut to your solution and modifying the working
directory.  It is interesting that the working directory of a shortcut
can influence build success.

- Tom 

-----Original Message-----
From: Gert Driesen [mailto:[EMAIL PROTECTED] 
Sent: Friday, February 25, 2005 2:52 PM
To: Whitner, Tom
Subject: RE: [Nant-users] RE: Strong Names - Delay Signing - Relative
Paths

Hi Tom,

This was fixed since. I'll upload a new nightly build soon.

Gert 

> -----Original Message-----
> From: Whitner, Tom [mailto:[EMAIL PROTECTED] 
> Sent: vrijdag 25 februari 2005 18:45
> To: Gert Driesen
> Subject: RE: [Nant-users] RE: Strong Names - Delay Signing - 
> Relative Paths
> 
> Gert,
> 
>       Any luck with this?
> 
> - Tom 
> 
> -----Original Message-----
> From: Gert Driesen [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, February 23, 2005 2:27 AM
> To: Whitner, Tom; nant-users@lists.sourceforge.net
> Subject: RE: [Nant-users] RE: Strong Names - Delay Signing - Relative
> Paths
> 
> Hi Tom,
> 
> I'm working on a fix for this issue, which will be committed 
> later today
> or
> tomorrow.
> 
> Gert 
> 
> > -----Original Message-----
> > From: [EMAIL PROTECTED] 
> > [mailto:[EMAIL PROTECTED] On Behalf Of 
> > Whitner, Tom
> > Sent: dinsdag 22 februari 2005 22:16
> > To: nant-users@lists.sourceforge.net
> > Subject: [Nant-users] RE: Strong Names - Delay Signing - 
> > Relative Paths
> > 
> > Ok,
> > 
> >     I've done a little more testing and found that VS2003 will allow
> > you to specify the path in the AssemblyKeyFile relative to 
> the output
> > directory (standard but crazy) or relative to the solution directory
> > (preferable to me).  The <solution> task, however, only supports the
> > first option.  Assuming I am correct, would it be possible 
> to make the
> > <solution> task behave the same as VS2003?  I a have a small example
> > that demonstrates this, but essentially it boils down to 
> either of the
> > following work in VS2003:
> > 
> > [assembly: AssemblyDelaySign(true)]
> > #if DEBUG
> > // Relative to solution folder
> > [assembly: AssemblyKeyFile(@"keypub.snk")]
> > #else
> > // Relative to output folder
> > [assembly: AssemblyKeyFile(@"..\..\keypub.snk")]
> > #endif
> > 
> > But only the second works with the NAnt <solution> task.
> > 
> > - Tom
> > 
> > 
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from 
> > real users.
> > Discover which products truly live up to the hype. Start 
> reading now.
> > http://ads.osdn.com/?ad_ide95&alloc_id396&op=ick
> > _______________________________________________
> > Nant-users mailing list
> > Nant-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nant-users
> > 
> > 
> 
> 
> 



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
Nant-users mailing list
Nant-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to