COM+ Application Creation

I have some c#, .net 2 code which creates and removes web sites,
virtual directories etc. It sits in a library and is used by a bunch
of in-house setup programs. It uses ADSI under the hood.

Whilst this library seems to work well, we've noticed something a
little strange. On the server where the web site is created, a COM+
Application called

IIS-{//Root}

is created. Now, our bespoke code does not create this entry directly,
although it does create a Web Application Pool, which I think is
related. The thing is, however, that although the uninstall process
appears to be clean (i.e. everything cleared out of the directory),
these COM+ entries appear to be left behind.

So, over the course of time, several application installs equate to
several (identical) COM+ applications, and everything starts to look a
bit untidy.

This happens on IIS6, but also on IIS5. (The in-house code only tries
to create application pools on IIS6.)

Does anyone know:

(a) exactly what this entry refers to?
(b) whether it is dangerous to have multiple identical entries in
here?
(c) the flip question, whether it is safe to delete excess entries?
(c) (pushing my luck here!) whether/how it is possible to ensure these
excess entries get removed just by manipulating properties on the web
site (i.e. something that I can set using ADSI)? At least then I could
have our code modified accordingly.

Grateful for any light that can be shed on this. TIA

Re: COM+ Application Creation

After a little more research, the answer to (a) is that it is created
as a result of setting the isolation level of the new web site's root
virtual directory. We use high isolation and this will not be allowed
to change.

This is a known bug, apparently, in IIS5 (not "known" in IIS6 as far
as I can tell, but believe me it exists!) Uninstalling a Web Site
doesn't uninstall the COM+ application.

Questions (b) thro' (d) still stand. Thanks