Hi,
I'm currently looking into moving the gac task from NAntContrib to NAnt, but
I'd like to propose moving to the following task layout :
<gac action="Install | Uninstall" force="true | false">
<assemblies>
<assembly name="..." reference="true | false" scheme="UninstallKey |
FilePath | Opaque" id="..." description="..." />
</assemblies>
</gac>
For the Install action, the name attribute of the assembly element would be
an actual filename, while for the Uninstall action the name attribute should
contain the (fully qualified) assembly name of the assembly that should be
uninstalled.
All other attributes (reference, scheme, id and description) are used for
adding / removing reference counts for the assembly. The reference
attribute is actually just used to indicate whether a reference should be
added/removed or not.
I'm not sure how useful the reference stuff is. If we choose not to
implement the reference stuff, we can possible install or uninstall all
assemblies in one go as gacutil accepts an option when you can specify a
file containing assemblies to install/uninstall, but this does not work when
you also need to add/remove references.
In the current NAntContrib, a fileset can be used to specify the assemblies
to install | uninstall. But I don't think this is a good idea as that would
only be useful for installing assemblies into the gac, not for removing them
(as you need the (fully qualified) assembly name, not the filename for
removing assemblies from the gac).
If we choose not to support references, we could split it up into two tasks
(or possible even more, as you could also create a task for deleting/list
the download cache and stuff). That way we can have fileset support for the
gac-install task, while using an optionset or something for the uninstall
task.
Would having support for references be useful ? To be honest, I'd rather
have a task that offers as much as functionality from the wrapped tool as
possible, even if I don't see any use for it right now and even if that
means that we'll loose fileset support. Installing numerous assemblies
using patterns isn't such a common task anyway, I assume.
What do you think ?
Gert
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
