> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Gert Driesen
> Sent: Thursday, December 02, 2004 22:59
> To: 'Jim Geurts'; 'John Cole'
> Cc: [EMAIL PROTECTED]
> Subject: RE: [Nant-users] 0.85 msi install
[snip]
> > 3. Install NAnt to C:\Program Files\NAnt. Install NAntContrib to
> > c:\Program Files\NAnt\NAntContrib. Again, with the option to put the
> > NAntContrib bin files in NAnt's main bin.
>
> I would prefer option 3 without an option to install the NAntContrib files
> in the NAnt bin directory, as this is really not recommended.
Hi Gert,
You keep discouraging this and recommend the use of "loadtasks" instead.
However, this means that the build-scripts become dependend on having the
correct path to the "nantcontrib" folder. In your examples on how
to do this, you hardwire that path in the script; clearly, this is not
acceptable in almost any situation.
Three ways of providing the necessary indirection come to mind:
1.1. require the path to be supplied on the commandline [pain in the neck].
1.2. require the path to be configured in an environment variable [shudder].
1.3. set the path in a global property in the nant config file.
On the other hand, if most or all of your build scripts make use of
nantconrib,
you may want to apply the DRY-principle and eliminate the repetitive
"loadtask-mantra" by having nantcontrb loaded by default. This *is* a
legitimate desire.
Three ways of achieving this are
2.1. copy nantcontrib/bin into nant/bin [crude]
2.2. create a link: nant/bin/tasks --> nantcontrib/bin [obscure & leads to
warnings]
2.3. add the appropriate <include .../> to the assemblies section in the
nant config file.
I think, but maybe someone has a better idea, that the cleanest solutions
are 1.3 and 2.3, i.e. edit the nant config file:
A. this is what config files are for, after all.
B. not resorting to some machine-wide configuration means one can have
multiple
nant versions side by side, each configured to use the appropriate
version
of nantcontrib.
Adding --if not already present-- the appropriate information to
nant.exe.config
should be no problem for a nantcontrib-installer. I think it would be good
if
the install routine would support both explicit load (1.3) and implicit load
(2.3)
More problematic is a nant-installer that preserves existing custom
configuration.
It might be a good idea to extend nant so that is also loads setting from
nant.exe.custom.config (if existent).
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
