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
A
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-
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
---
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
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 I
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.d
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
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 m
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 pu
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
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
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 (
)
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-use
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
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
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 p
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/
> -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 comm
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
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.
Merr
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, h
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
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 th
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
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
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
> Sub
26 matches
Mail list logo
