Yup, you're right. I've just tries it in C# and it's a no go. VB seems to cope OK with referencing the .snk from the source directory. Interestingly, if you create a blank project in both languages, the C# one has helpful tips in the AssemblyInfo.cs file on how to create and reference a keyfile and states that it will be referenced from the output folder. The AssemblyInfo.vb file says nothing about signing assemblies or what to do.
I've decided to change the structure of how I build stuff in the end and build to the same folder structure as VS does then copy the files else where if needed. This does at least give me the possibility of building debug and release versions in the same script without overwriting them. Cheers, Bill -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 30 March 2004 11:13 To: Bill Martin; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: AW: [Nant-users] Solution Task and Strong Names >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Sent: Tuesday, March 30, 2004 07:19 AM >To: [EMAIL PROTECTED] >Cc: [EMAIL PROTECTED] >Subject: RE: AW: [Nant-users] Solution Task and Strong Names > >"... Are you sure this works from Visual Studio ? From what I've read you >should ..." > > >It definitely works I tried this with a C# project and VS.NET was not able to locate the key file. I'll try this using VB.NET later. >The alternative is to use the <args> element in the <vbc> task to explicitly >pass the location of the key file when I compile the application. So, you're not using the <solution> task ? Gert ______________________________________________________________ CONFIDENTIALITY NOTICE This communication and the information it contains is intended for the person or organisation to whom it is addressed. Its contents are confidential and may be protected in law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you are not the intended recipient, please contact us immediately. The contents of any attachments in this e-mail may contain software viruses, which could damage your own computer system. While Marlborough Stirling has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage, which you sustain as a result of software viruses. You should carry out your own virus checking procedure before opening any attachment. Marlborough Stirling plc, Registered in England and Wales Registered No. 3008820, Allen Jones House, Jessop Avenue, Cheltenham, Gloucestershire, GL50 3SH Tel: 01242 547000 Fax: 01242 547100 http://www.marlborough-stirling.com ------------------------------------------------------- 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_id70&alloc_id638&op=click _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
