I was just wondering if anybody could guide me towards options of
exposing a .Net dll so that it can be added to COM+ application.

I haven't been able to use System.EnterpriseServices, because I can't
strong name my assembly (due to third party references which are not
strong named).

Regasm probably will not work for my solution, as our tool tries to go
and manually register each of these components with MTS.

I could try manually adding a registry key with the code base and other
info, but I was under the impression that this in theory was what
Regasm was doing.

My main problem being that I am basically providing a plug-in for a
third party software. I have little details of how they actually
create/maintain an instance - Late bind / early bind/ what?

Prad,

Unfortunately, in order to place a component in COM+, you really have to
use the classes in the System.EnterpriseServices namespace. There really is
no other option. You might have to cut the third-party references that are
not strong named, or push the vendor to provide strong names for their
assemblies.

Hope this helps.

--
- Nicholas Paldino [.NET/C# MVP]
- (E-Mail Removed)

"Prad" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I was just wondering if anybody could guide me towards options of
> exposing a .Net dll so that it can be added to COM+ application.
>
> I haven't been able to use System.EnterpriseServices, because I can't
> strong name my assembly (due to third party references which are not
> strong named).
>
> Regasm probably will not work for my solution, as our tool tries to go
> and manually register each of these components with MTS.
>
> I could try manually adding a registry key with the code base and other
> info, but I was under the impression that this in theory was what
> Regasm was doing.
>
> My main problem being that I am basically providing a plug-in for a
> third party software. I have little details of how they actually
> create/maintain an instance - Late bind / early bind/ what?
>