Guiseppe and I had a conversation about this a while back (sorry Guiseppe, I got busy and never got it fully working) and it looks like a bit of work.You need a reader that can resolve external entities (out of the box, only the validating reader does this), but then I recall that Guiseppe's
it is possible that a future EnumValidatorAttribute
would limit the enum to only a few values.
Can you describe a usage scenario? (or are you just commenting on how things
should be?)
- Original Message -
From: Gordon Weakliem [EMAIL PROTECTED]
Looking
I've started writing a tutorial on creating custom tasks, I thought I'd throw the
first draft out for comments. I've attached my draft as well as a copy of the custom
task that I'm using as the basis for the tutorial. I'd appreciate any feedback
people have. The early parts of the article
There was some discussion of this about a month ago, IIRC it turned out to not be easy
to do. This is actually a good FAQ item, I took the liberty of adding it to the FAQ.
-Original Message-
This discussion does bring up another interesting point though, which is
more general
I'm not sure I really understand the situation, but I'll take a crack.
Ben Singh wrote:
In this example I have a core.dll, customer.dll, customerWS.dll and a
businessportal.dll. If something in businessportal.dll changes then as far
as I know a complete build needs to be performed.
I'm
://lists.sourceforge.net/lists/listinfo/nant-developers
// Copyright (C) 2002 Gordon Weakliem
//
// This program is free software; you can redistribute it and/or modify
// it under the terms of the GNU General Public License as published by
// the Free Software Foundation; either version 2 of the License
I've been working on something along the same lines, except that we're doing C# and C++. Essentially, there's a build file which uses the style task to convert a .csproj file to .build, then uses the nant task to build it. I'm amusing myself so much with this that I'll probably finish it whether
