Hello Friends,
I am maintaining our property files in the format of .build files itself. Like:
But our client wants this property file, like ANT property file with extension as ".property" and structure (may be he want to use same file in ANT also), like this
buil
[snip]
-> Yes, do tell. I'm having the opposite problem: when I
-> redirect the output to a file, it *still* shows up in the
-> NANT log even though I don't want it to...
Here is a convoluted example of how I call to dump
Subversion repositories using file redirection:
Have a
look on the Sourceforge site for a tool called vb.doc
This
does the extract of comments from VB code, either through a GUI, command line or
through its own NAnt task. You can then use the NDoc task on the resulting
xml and compiled assemblies.
You
may have to edit the tool or yo
Title: performance issue in resource generation - for VB projects
I think I have discovered a performance issue with resource generation on large builds – it is VB specific.
Long story short: For each resource file in a project, the entire reference structure of your project is traversed and
Gary Feldman said:
> Bill Bither wrote:
>
>>Is there an easy way to force the output from an EXEC task to be written
>>to the console, so that the NAnt log includes the output from the
>>external commandline application?
>>
> This is the default behavior. Are you seeing something different?
Yes,