> ----- Original Message -----
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, March 29, 2004 9:31 AM
> Subject: RE: AW: [Nant-users] Solution Task and Strong Names
>
> I'm slightly confused (it doesn't take much!). Which tasks have been
> modified?
The <solution> task has been modified. We now set the current working
directory to %Project Directory%\obj\<configuration> (see below).
> I raised the same problem last week (see "Problem with vbc task"
> post) and Gert kindly provided the response that VS tries the path to the
> Key file first from the current directory, and if it can't find it there,
> then from the output directory. As a result of this, I then changed my
> AssemblyInfo.vb file to be:
>
> <Assembly: AssemblyKeyFile("Component.snk")>
>
> and this seems to work fine both within Visual Studio and from my NAnt
> script (I'm using 0.84).
Are you sure this works from Visual Studio ? From what I've read you should
specify the assemblykeyfile as "a path relative to the project output
directory which is / %Project Directory%\obj\<configuration>. For example,
if your KeyFile is located in the project directory, you would specify the
AssemblyKeyFile
attribute as [assembly: AssemblyKeyFile("..\\..\\mykey.snk")]".
> Will this now break as a result of changes made
> when I upgrade to 0.85?
You might have to change your attribute to
<Assembly: AssemblyKeyFile("..\\..\\Component.snk")>
Gert
-------------------------------------------------------
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-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
