Hello all,
I was wondering if there's a way I could use the script task to implement nant 0.85's
string::replace function. Is it possible to do this in nant 0.84? If so, how?
Thanks,
Felice
---
This SF.Net email is sponsored by BEA Weblog
Unfortunately I cannot. The project involved is sensitive in nature and
I can't demonstrate any of the source. If I get time I'll see if I can
reduce the problem to a minimal set that is sanitized. In the meantime,
I have worked around the problem by uisng an exec call to devenv which
builds the
Steve,
Can you provide a small repro for this issue ?
Thanks,
Gert
- Original Message -
From: "Steve Mitcham" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 27, 2004 6:00 PM
Subject: [Nant-users] Bad COM registration
I am using the latest nightly build (8/25 I believe).
I am using the
latest nightly build (8/25 I believe). I am having a problem with a C++
COM server dll and the solution task. When I build the DLL from inside the
IDE everything is fine, however, when I build the DLL through the nant solution
task I am getting a 0x80070002 error when attemp
Title: RE: [Nant-users] Properties Descriptions
Merrill,
/* ... */ and // ... style comments cannot be pinned to a language element any more than a style comment can. I think it is generally accepted that comments precede the thing that they describe.
Having said that, I suppose the 'comme
You could fake it by calling within its own target. Something
like:
Then you can depend on that project using the normal depends attribute:
...
The naming is still problematic, but at least you don't need to have one
huge build file.
--
Edwin G. Castro
Firing Systems Engineer
[EMAIL
I really like this idea. I know we've toyed with the idea of a .build xslt which could be used to make a more 'natural' published build to our CM website and comments would make it that much better.
Original Message Follows
From: Merrill Cornish <[EMAIL PROTECTED]>
Reply-To: Merrill Cor
Member, method/function/procedure and class comments can easily fall in the same area
you're talking about with these comments, and I don't think too many folks get overly
lost with those...
You've got a nice point, but my $0.02 is that I'd rather see the developers working
other issues unless
Jim,
>>> How would this differ from using XML comments in the build files?
Clumsiness, or lack thereof.
or
versus
XML comments are verbose and stand on a level with the elements they are supposed to
be commenting on. Therefore, it's not always clear who they
>>Perhaps NAnt could allow, but ignore, a "comment" attribute on all tasks.<<
How would this differ from using XML comments in the build files?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Merrill Cornish
Sent: Friday, August 27, 2004 10:05 AM
To: Gert Dr
Gert,
>>> [property descriptions] has never been supported by NAnt ... NAnt now reports
>>> unknown elements and attributes.
Perhaps NAnt could allow, but ignore, a "comment" attribute on all tasks.
Merrill
---
SF.Net email is sponsored by
David,
This has never been supported by NAnt. What has changed in recent nightly
builds, is that NAnt now reports unknown elements and attributes. Previous
versions of NAnt did not have this capability.
Gert
- Original Message -
From: "Shaber, David" <[EMAIL PROTECTED]>
To: <[EMAIL PROT
12 matches
Mail list logo