Component in COM+ No Enterprise Services

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

cksj - 22 Sep 2004 17:40 GMT

What are the implications of an assembly written VB.Net that is
registered in COM+ but is not referencing the Enterprise Services? We
have a couple of programmers who develops assemblies (no reference to
Enterprise Services) and likes to stick it to COM+. Basically, the
assemblies has no knowledge of COM+, but it is running in our web
server in COM+.

We're getting a lot of COM surrogate errors and I'm guessing it's
because of these assemblies.

Thanks for any input.

Cesar

Reply to this Message

Jos? Miguel Torres - 29 Sep 2004 14:27 GMT

The componente registered is not able to use COM+ Services as transactions,
JIT, object pooling, and more. To use componente without ServicedComponent
reference is like COM+ library component.
regards

--
Jos? Miguel Torres
jtorres_diaz~~ARROBA~~terra.es
http://jmtorres.blogspot.com

> What are the implications of an assembly written VB.Net that is
> registered in COM+ but is not referencing the Enterprise Services? We
[quoted text clipped - 9 lines]
>
> Cesar

Reply to this Message

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...