Title: Message
Hi
Jarek,
I
think a set of standards for NAnt build files would be awesome. The
documentation would be a great driver for a GUI tool, and although there are a
number of examples in the NAnt source files but the addition of a GUI
designer would probably help out a lot with
Gary,
>>> why can't they both be good?
They might be, in one situation or another. I would like a Best Practices document to
give me a hint as to what those situations are.
Merrill
---
This SF.Net email is sponsored by: YOU BE THE JUDGE. B
>From: "Merrill Cornish" <[EMAIL PROTECTED]>
>Sent: Thursday, September 09, 2004 12:40 PM
> I've used a number of large, commercial, and apparently
>well-documented software packages--only to find that what
I certainly agree with you on the need. My take is that it's more
in the Cookbook or Re
Gary,
>>> and "best" implies everything else is worse,
I've used a number of large, commercial, and apparently well-documented software
packages--only to find that what I really needed _was_ a "best practices" document.
There is a great tendency of documenters to fall into the rut of writing,
>From: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>
>Sent: Thursday, September 09, 2004 8:34 AM
>Do you think it would be feasible to create something
>like a ".NET OSS Build Standard" based on nant scripts
>that could then be adopted by all the projects. I think that
>it would greatly simplify the
Title: Message
As
someone that is 4 months into NAnt, I think that is an excellent idea. It
really took me a lot to understand what the best practices and standards
are. This is because they are unspoken, kind of implied. However, if
you are new to 1) configuration management and 2) build
