a "standard" setup? That would be a beautiful thing
IMO :-).
Great
idea!
Cheers,
Clayton
-Original Message-From:
Jaroslaw Kowalski [mailto:[EMAIL PROTECTED] Sent: September 9, 2004
5:35 AMTo: [EMAIL PROTECTED]Subject:
[Nant-users] Build process unificat
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
, 2004 8:35 AMTo:
[EMAIL PROTECTED]Subject: [Nant-users] Build process
unification
Hi!
Inspired by the Gump project, I started
looking at various open source projects (log4net, NDoc, NAnt, NUnit,
ICSharpCode.*) to see how they are built and how they
interoperate.
The
Hi!
Inspired by the Gump project, I started
looking at various open source projects (log4net, NDoc, NAnt, NUnit,
ICSharpCode.*) to see how they are built and how they interoperate.
The typical problem is: you want to build a
component (one or more DLLs + some EXEs) based on a set of other
