[Nant-users] file::exists() problem
How do I use the task to check for the existence of
a file where the file name is stored in a property?
The documentation shows
...
but trying to do the following does not seem to work.
It appears that the ${file.to.check} is not expanded but
taken literally
Any ideas?
Joe Uchytil
RE: [Nant-users] file::exists() problem
You are
already in an expansion, so you don't need the expansion round your
property. Try:
Cheers,
Bill
-Original
Message-
From: Joe Uchytil
[mailto:[EMAIL PROTECTED]
Sent: 22 February 2005 13:58
To:
nant-users@lists.sourceforge.net
Subject: [Nant-users]
file::exists() problem
How do I use the task to check
for the existence of a file where the file name is stored in a property?
The documentation shows
...
but trying to do the following does not
seem to work.
It appears that the ${file.to.check} is
not expanded but taken literally
Any ideas?
Joe Uchytil
UK businesses use 2 million tonnes of paper each year.
THINK before you PRINT this email.
__
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,
Jessop House, Jessop Avenue, Cheltenham, Gloucestershire, GL50 3SH
Tel: 01242 547000 Fax: 01242 547100
http://www.marlborough-stirling.com
RE: [Nant-users] file::exists() problem
Joe,
What
you want to do is this:
HTH,
Felice
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of Joe
UchytilSent: Tuesday, February 22, 2005 7:58 AMTo:
nant-users@lists.sourceforge.netSubject: [Nant-users]
file::exists() problem
How do I use the task
to check for the existence of a file where the file name is stored in a
property?
The documentation
shows
...
but trying to do the following
does not seem to work.
It appears that the
${file.to.check} is not expanded but taken literally
Any ideas?
Joe Uchytil
Re: [Nant-users] file::exists() problem
--- 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_id=6595&alloc_id=14396&op=click ___ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
Re: [Nant-users] file::exists() problem
Joe, Put quotes around the argument to exists() if you are specifying a literal file name. Leave off the quotes of the argument is a property name that needs to be evaluated to get the file name. Merrill --- 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_id=6595&alloc_id=14396&op=click ___ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
[Nant-users] Difference between importing a OCX in VS and running AXIMP?
Hi there, I want my software to be strong named. So my NANT task runs AXIMP to import a wrapper for an ActiveX Control. However the result is different from the interaction in Visual Studio. In VS I get 2 files: AxInterop.wmplib.dll and Interop.wmplib.dll. In AXIMP I get Axwmplib.dll and wmplib.dll and some differences in the content (get some errors on execution). Am I missing switches? :-? stw
Re: [Nant-users] Difference between importing a OCX in VS and running AXIMP?
I don't think you are missing switches. As a matter of fact, I just emailed Gert directly yesterday about this issue. There is even a comment in the code that says it is being assumed that Interop.* will suffice and the call to AxImp uses the "/rcw" parameter. The work around I found so far is to run the exact same AxImp command without the "/rcw" parameter, this forces the creation of the AxInterop.* file. I don't know enough to say that the rcw parameter should just not be used but other than performance, I don't see how it would hurt to not make the assumption I mentioned above and never use the rcw parameter. Gert, would you enlighten us?? :-) Thanks! [EMAIL PROTECTED] wrote: Hi there, I want my software to be strong named. So my NANT task runs AXIMP to import a wrapper for an ActiveX Control. However the result is different from the interaction in Visual Studio. In VS I get 2 files: AxInterop.wmplib.dll and Interop.wmplib.dll. In AXIMP I get Axwmplib.dll and wmplib.dll and some differences in the content (get some errors on execution). Am I missing switches? :-? stw
RE: [Nant-users] user submitted
I have added a few more. One to start SQL server and one to execute a query to an ODBC datasource. I'll see about adding more. John Cole -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ian MacLean Sent: Sunday, February 20, 2005 7:47 AM To: NAnt Users mailing list Subject: [Nant-users] user submitted
[Nant-users] Strong Names - Delay Signing - Relative Paths
Title: Strong Names - Delay Signing - Relative Paths Hello, Is anyone out there actually signing assemblies? I am working through automating this with NAnt. Of course, I want the process to actually sign the assemblies when run on our build server, but only partially sign (with public key only) when built on a developer's workstation. Also, I want the solution to build with both NAnt and Visual Studio. I figured key containers would simplify this. However, I have not been able to install just the public key into a container. So, I am back to key files for the developer builds. Unfortunately, if I set the relative path in the KeyFile attribute to work from VS, the build fails from NAnt. I am using the task to build the solution. Could this be a bug in the solution task? Thanks, Tom
[Nant-users] Strong Names - Delay Signing - Relative Paths
Title: Strong Names - Delay Signing - Relative Paths I just discovered an article (http://blogs.msdn.com/shawnfa/archive/2004/04/15/114258.aspx) that indicates that the path in the AssemblyKeyFile attribute is relative to the output folder. This is insane yet explains why my NAnt build fails while my VS build succeeds. Each has different output directories. Thankfully, this looks to be fixed in Whidbey. Any thoughts on how to tackle with w/o another build config? - Tom -- Hello, Is anyone out there actually signing assemblies? I am working through automating this with NAnt. Of course, I want the process to actually sign the assemblies when run on our build server, but only partially sign (with public key only) when built on a developer's workstation. Also, I want the solution to build with both NAnt and Visual Studio. I figured key containers would simplify this. However, I have not been able to install just the public key into a container. So, I am back to key files for the developer builds. Unfortunately, if I set the relative path in the KeyFile attribute to work from VS, the build fails from NAnt. I am using the task to build the solution. Could this be a bug in the solution task? Thanks, Tom
RE: [Nant-users] Strong Names - Delay Signing - Relative Paths
Title: Strong Names - Delay Signing - Relative Paths Have your script copy the key to the relative path. Payton Byrd Trane eBusiness QED Team Phone: 931-905-5386 Fax: 931-648-5901 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Whitner, Tom Sent: Tuesday, February 22, 2005 1:12 PM To: nant-users@lists.sourceforge.net Subject: [Nant-users] Strong Names - Delay Signing - Relative Paths I just discovered an article (http://blogs.msdn.com/shawnfa/archive/2004/04/15/114258.aspx) that indicates that the path in the AssemblyKeyFile attribute is relative to the output folder. This is insane yet explains why my NAnt build fails while my VS build succeeds. Each has different output directories. Thankfully, this looks to be fixed in Whidbey. Any thoughts on how to tackle with w/o another build config? - Tom -- Hello, Is anyone out there actually signing assemblies? I am working through automating this with NAnt. Of course, I want the process to actually sign the assemblies when run on our build server, but only partially sign (with public key only) when built on a developer's workstation. Also, I want the solution to build with both NAnt and Visual Studio. I figured key containers would simplify this. However, I have not been able to install just the public key into a container. So, I am back to key files for the developer builds. Unfortunately, if I set the relative path in the KeyFile attribute to work from VS, the build fails from NAnt. I am using the task to build the solution. Could this be a bug in the solution task? Thanks, Tom
[Nant-users] string literals
When I execute the equivalent of the below lines from command line, InstallShield wants quotes around the second part of the parameter. For instance -c "Release 1" is required. How do I force the string literals to do the same thing in the task? Adding the double quotes around the parameter ( ) doesn't work either, in fact causes the following error: Error loading buildfile. This is an unexpected token. The expected token is 'NAME'. Line 129, position 21. What I have now... But causes this error... [exec] -1113: The 'p C:\MAP\Applications\DevInt\Install_Shield\NWEA_MAPAdminWebWeb_Install.ism' switch is not recognized. Thanks in advance for any assistance. ~Robert --- 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_id=6595&alloc_id=14396&op=click ___ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
RE: [Nant-users] string literals
It's still just xml so you can use something like this: the " will add in the quotations for you. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert Smith Sent: Tuesday, February 22, 2005 1:38 PM To: nant-users@lists.sourceforge.net Subject: [Nant-users] string literals When I execute the equivalent of the below lines from command line, InstallShield wants quotes around the second part of the parameter. For instance -c "Release 1" is required. How do I force the string literals to do the same thing in the task? Adding the double quotes around the parameter ( ) doesn't work either, in fact causes the following error: Error loading buildfile. This is an unexpected token. The expected token is 'NAME'. Line 129, position 21. What I have now... But causes this error... [exec] -1113: The 'p C:\MAP\Applications\DevInt\Install_Shield\NWEA_MAPAdminWebWeb_Install.is m' switch is not recognized. Thanks in advance for any assistance. ~Robert --- 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_id=6595&alloc_id=14396&op=click ___ 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
[Nant-users] Problems compiling a Unmanaged project in a solution file
Title: Problems compiling a Unmanaged project in a solution file We have a solution file that is mostly c# projects, however it also has one unmanaged project in it and one managed project in it. I call the solution build and hand it the solution file, however, NAnt doesn’t seem to like the new managed or unmanaged projects. I get a null reference exception when I try to run the build. This is the error message that I get: System.NullReferenceException: Object reference not set to an instance of an object. Has anyone experienced this before and been able to compile a “mixed” solution like this? I am using NAnt 0.85 RC2. Thanks, Marisa
RE: [Nant-users] Strong Names - Delay Signing - Relative Paths
Title: Strong Names - Delay Signing - Relative Paths I get the following error "error CS1548: Cryptographic failure while signing assembly 'MyAssembly.dll' -- 'Error reading key file 'A.snk' -- The system cannot find the file specified. ' " I found this knowledge base article http://support.microsoft.com/default.aspx?scid=kb;en-us;328379 which references to VS2002. My experimenting has shown that this path is now relative to the sln file in VS2003. I am suspecting this is an issue with the task and C#. - Tom From: Foster, Richard - PAL [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 22, 2005 2:29 PMTo: Whitner, TomSubject: RE: [Nant-users] Strong Names - Delay Signing - Relative Paths Tom, In what way does the build fail within NAnt? Is it by any chance complaining about running the tests? If so, you probably need to add an appropriate validation entry on your build machine (E.g. use sn -Vr *,). In our configuration we use the task to set the appropriate public key file (using an absolute path in a NAnt property), then use the task on our continuous integration machine to complete the signing process after a successful build & test cycle. Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Whitner, TomSent: Tuesday, February 22, 2005 13:51To: nant-users@lists.sourceforge.netSubject: [Nant-users] Strong Names - Delay Signing - Relative Paths Hello, Is anyone out there actually signing assemblies? I am working through automating this with NAnt. Of course, I want the process to actually sign the assemblies when run on our build server, but only partially sign (with public key only) when built on a developer's workstation. Also, I want the solution to build with both NAnt and Visual Studio. I figured key containers would simplify this. However, I have not been able to install just the public key into a container. So, I am back to key files for the developer builds. Unfortunately, if I set the relative path in the KeyFile attribute to work from VS, the build fails from NAnt. I am using the task to build the solution. Could this be a bug in the solution task? Thanks, Tom
[Nant-users] Re: string literals
Thanks for the help, here's the syntax that made it succeed(note the " ): ~Robert On Tue, 22 Feb 2005 11:37:54 -0800, Robert Smith <[EMAIL PROTECTED]> wrote: > When I execute the equivalent of the below lines from command > line, InstallShield wants quotes around the second part of the > parameter. > > For instance -c "Release 1" is required. How do I force the string > literals to do the same thing in the task? > > Adding the double quotes around the parameter ( /> > ) doesn't work either, in fact causes the following error: > > Error loading buildfile. > This is an unexpected token. The expected token is 'NAME'. Line 129, > position 21. > > What I have now... > > > > > > > > But causes this error... > > [exec] -1113: The 'p > C:\MAP\Applications\DevInt\Install_Shield\NWEA_MAPAdminWebWeb_Install.ism' > switch is not recognized. > > Thanks in advance for any assistance. > > ~Robert > -- Robert Smith [EMAIL PROTECTED] --- 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_id=6595&alloc_id=14396&op=click ___ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
[Nant-users] Can't get NUnit to work with Nant
Hey everyone, Been struggling with a problem at work. Compiled with 2.2.2.0 but nant keeps saying Internal Error: System.IO.FileLoadException The located assembly's manifest definition with name 'nunit.core' does not match the assembly reference. So I even changed the libraries out in the lib/net/1.1/nunit* nothing advice would be great! Thanks, Chris --- 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_id=6595&alloc_id=14396&op=click ___ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
RE: [Nant-users] string literals
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Robert Smith > Sent: dinsdag 22 februari 2005 20:38 > To: nant-users@lists.sourceforge.net > Subject: [Nant-users] string literals > > When I execute the equivalent of the below lines from command > line, InstallShield wants quotes around the second part of the > parameter. > > For instance -c "Release 1" is required. How do I force the string > literals to do the same thing in the task? > > Adding the double quotes around the parameter ( > ) doesn't work either, in fact causes the following error: > > Error loading buildfile. > This is an unexpected token. The expected token is 'NAME'. Line 129, > position 21. > > What I have now... > > > > > > > > But causes this error... > > [exec] -1113: The 'p > C:\MAP\Applications\DevInt\Install_Shield\NWEA_MAPAdminWebWeb_ Install.ism' > switch is not recognized. > > Thanks in advance for any assistance. The best solution is splitting up the first argument in two separate args: When you use the "file" attribute, NAnt will automatically resolve a relative path to an absolute path and apply quoting if necessary. Gert --- 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_id=6595&alloc_id=14396&op=click ___ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
[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 task, however, only supports the first option. Assuming I am correct, would it be possible to make the 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 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=click ___ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
Re: [Nant-users] Re: string literals
Robert, I think there's another solution that's a little prettier. XML allows either single _or_ double quotes to be used to delimit attributes. So, if you use single quotes to delimit that particular arg attribute, then you are free to use double quotes within that single quoted string. Merrill --- 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_id=6595&alloc_id=14396&op=click ___ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
RE: [Nant-users] Re: string literals
Here is another alternative: -- Edwin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert Smith Sent: Tuesday, February 22, 2005 1:00 PM To: nant-users@lists.sourceforge.net Subject: [Nant-users] Re: string literals Thanks for the help, here's the syntax that made it succeed(note the " ): ~Robert On Tue, 22 Feb 2005 11:37:54 -0800, Robert Smith <[EMAIL PROTECTED]> wrote: > When I execute the equivalent of the below lines from command > line, InstallShield wants quotes around the second part of the > parameter. > > For instance -c "Release 1" is required. How do I force the string > literals to do the same thing in the task? > > Adding the double quotes around the parameter ( > ) doesn't work either, in fact causes the following error: > > Error loading buildfile. > This is an unexpected token. The expected token is 'NAME'. Line 129, > position 21. > > What I have now... > > > > > > > > But causes this error... > > [exec] -1113: The 'p > C:\MAP\Applications\DevInt\Install_Shield\NWEA_MAPAdminWebWeb_Install.is m' > switch is not recognized. > > Thanks in advance for any assistance. > > ~Robert > -- Robert Smith [EMAIL PROTECTED] --- 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_id=6595&alloc_id=14396&op=click ___ 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
[Nant-users] task question
Should -projecthelp display targets which are included with the task? --- 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_id=6595&alloc_id=14396&op=click ___ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
[Nant-users] More task woes
I am trying to use the Nant task to segregate related targets into include files, but it's not working. If I set verbose="true" on the include task, the output shows it is being included, but if I try to call a target in the included file explicitly or via depends, it says the target is not in the project. Any ideas? This is with 0.85 RC2. --- 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_id=6595&alloc_id=14396&op=click ___ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
Re: [Nant-users] More task woes
Bill, I haven't done it recently, but I've prviously been able to call targets (did you really mean "tasks") defined in an included NAnt script from the calling Nant script. Of course, the include must come before the call to the included target. Merrill --- 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_id=6595&alloc_id=14396&op=click ___ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
Re: [Nant-users] Difference between importing a OCX in VS and running AXIMP?
Hi Dante, thx for your reply. I see I need to be more specific. When I run the AXIMP task as defined in NANT it only created one file, but not two. So I used to run it through the command shell. Providing no switches and no output file name a OCX named wmplib.dll would result in Axwmplib.dll and (same name!) wmplib.dll using AXIMP and AxInterop.wmplib.dll and Interop.wmplib.dll in VS. Technically spoken this question doesn't belong here, since it is VS vs. .NET Framework tools. So what would be the right place to ask? :-) stw [EMAIL PROTECTED] wrote on 23/02/2005 02:32:43: > I don't think you are missing switches. As a matter of fact, I just > emailed Gert directly yesterday about this issue. There is even a > comment in the code that says it is being assumed that Interop.* > will suffice and the call to AxImp uses the "/rcw" parameter. The > work around I found so far is to run the exact same AxImp command > without the "/rcw" parameter, this forces the creation of the > AxInterop.* file. > > I don't know enough to say that the rcw parameter should just not be > used but other than performance, I don't see how it would hurt to > not make the assumption I mentioned above and never use the rcw > parameter. Gert, would you enlighten us?? :-) > > Thanks! > > > [EMAIL PROTECTED] wrote: > > Hi there, > > I want my software to be strong named. So my NANT task runs AXIMP to > import a wrapper for an ActiveX Control. However the result is > different from the interaction in Visual Studio. In VS I get 2 > files: AxInterop.wmplib.dll and Interop.wmplib.dll. In AXIMP I get > Axwmplib.dll and wmplib.dll and some differences in the content (get > some errors on execution). Am I missing switches? > > :-? stw
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 task, however, only supports the > first option. Assuming I am correct, would it be possible to make the > 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 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
