heers,
Arjen Poutsma
---
"To iterate is human, to recurse, divine."- L. Peter Deutsch
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which produc
Ian wrote:
[snip]
> so yes it needs some work but we are working on it.
I consider NAntContrib to be a playing ground for contributing
_developers_ to create new tasks, before these enter the main
repository. For this purpose, it functions perfectly. In fact, I wish
that the solution task, which
Ok, so it has been rejected ;-). That's fine, I just wanted to be sure.
> -Original Message-
> From: Ian MacLean [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 04, 2003 9:18 AM
> To: Arjen Poutsma
> Cc: [EMAIL PROTECTED]
> Subject: Re: [nant-dev] RE: Patch
Best,
Arjen
> -Original Message-----
> From: Arjen Poutsma
> Sent: Tuesday, August 26, 2003 10:15 AM
> To: '[EMAIL PROTECTED]'
> Subject: Patch: Case insensitive enum value lookups
>
>
> Hi,
>
> The attached patch for Element.cs allows case-insensi
I'm always in favor of more fileset support, so you have my vote!
> -Original Message-
> From: Gert Driesen [mailto:[EMAIL PROTECTED]
> Sent: Saturday, August 30, 2003 3:23 PM
> To: Nant-Developers (E-Mail)
> Subject: [nant-dev] Mail task
>
>
> Hi,
>
> Currently the mail task allows fi
Hi,
The attached patch for Element.cs allows case-insensitive lookup of
enumeration values in the build file.
A number of tasks use an enum to specify a closed set of task
parameters. For instance, the foreach task uses the LoopItem enum to
specify the type of iteration that should be done. With
If this is the policy, the RegSvcs Task should be changed accordingly.
The action attribute now requires an upper case argument: FindOrCreate,
Create, or Uninstall.
Thanks,
Arjen
> -Original Message-
> From: Ian MacLean [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 18, 2003 1:18 PM
>
Ok, I think I get it now :-). Basically, you want a fxcop task that can
be used as follows:
Which only checks the assemblies defined in the project file against the
rules defined in the project file.
Which checks the assemblies in the targets fileset agai
Ok, I think I get it now :-). Basically, you want a fxcop task that can
be used as follows:
Which only checks the assemblies defined in the project file against the
rules defined in the project file.
Which checks the assemblies in the targets fileset agai
t file,
like so:
But I don't think we can combine this with any of the attributes
described above.
Do these changes make it more useful?
Best,
Arjen
> -Original Message-
> From: Gert Driesen [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 11, 2003 9:42 PM
> To: Ar
Hi,
Attached to this file is the RevSvcs task. This task installs or removes
.NET Services.
It can be used as follows:
Adds all public classes contained in myTest.dll to a COM+ 1.0
application and produces the myTest.tlb type library. If the application
already exists, it is overwritten.
Adds
Hi,
I've created two new tasks. Before I post them to the list, I would like
to know it there's interest.
First, a wrapper Nant task for FxCop, which can be found at
http://www.gotdotnet.com/team/fxcop. This tools checks for compliance
with the .NET Design guidelines. The task basically wraps FxC
Hi,
The attached patch fixes some issues I had with the MSI task from
NantContrib:
- Some members of MSIComponent, as defined in the xsd, have changed
type, making it necessary to use setStringData instead of
setIntegerData, or vice-versa.
- The componentFiles fileset requires a Parent, otherwise
Hi,
Until now, I've always used the XsdTask (from NantContrib) to generate my
typed datasets from xml schemas. I've found that using this this task has
several disadvantages:
* You can't use filesets to generate datasets from a collections of xml schemas.
Since my entire build environment is bas
> I think we were still discussing the best way to implement
> the features in
> the looptask . Maybe we are just waiting on the work
> do be done,
> and the changes to be committed. I would not call this a show-stopper.
I agree: this is not a show-stopper.
After reading all possible solution
the directory which will contain the html. This should work.
A
> -Original Message-
> From: Griffin Caprio [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 20, 2003 8:31 PM
> To: Arjen Poutsma; Gerry Shaw
> Cc: Nant-Developers (E-mail)
> Subject: RE: [nant-dev] Substrin
, though.
A
> -Original Message-
> From: Matthew Mastracci [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 20, 2003 5:05 PM
> To: Arjen Poutsma
> Cc: [EMAIL PROTECTED]
> Subject: Re: [nant-dev] Patch to let LoopTask work with Filesets
>
>
> On issue with ad
Hi,
I've changed the LoopTask so that it uses Filesets for "item=File" loops, instead of
the current "in=[directory]" mechanism. This means that you can write foreach tasks
such as:
The "in=[directory]" mechanism still works too.
The patch is att
> -Original Message-
> From: Philip Nelson [mailto:[EMAIL PROTECTED]
> Sent: Sunday, March 16, 2003 3:13 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [nant-dev] bug in recursive source compile using
> A basedir of the current directory should be indicated as
> ".". "**/*.cs" means
> all .c
Hi,
Attached to this message is the RegexTask, which sets project properties based on the
evaluatuion of a regular expression. It is really quite simple, and fully documented.
Best,
Arjen
RegexTask.cs
Description: RegexTask.cs
> -Original Message-
> From: Gerry Shaw [mailto:[EMAIL PROTECTED]
> Sent: donderdag 13 maart 2003 18:53
> To: Arjen Poutsma
> Cc: Nant-Developers (E-mail)
> Subject: RE: [nant-dev] Substring?
[snip]
> I haven't followed the discussion about substring too close
I've already created such a regex task, which sets properties based on named Groups
().
For example, for the regular expression ^(?\w+):(?\w+), you'd say:
results in:
[echo] Section1
[echo] 119900
Note that you have to use the XML entity < in order to specify a <.
I could send it to the li
Hi,
When creating satellite assemblies based on .resources files for specific cultures, I
ran into some problems with the AlTask. The AlTask always embeds resource with a name
that is equal to the filename of the resource. Visual Studio uses the namespace as a
prefix for this name. In other wor
23 matches
Mail list logo
