Issue in DCOM

hi friends,

What is the advantage of using ActiveX EXE insted of using ActiveX DLL while developing DCOM Components.


please answer me.
with regards
prince

I would use COM+ and avoid ActiveX EXE's

Quote:

---

Originally posted by yrwyddfa
I would use COM+ and avoid ActiveX EXE's

---

hi,

Even if you are using COM+ also, you need to create components in either ActiveX DLL or ActiveX EXE. My question is DLL's are In-process and EXE's are out-ofprocess, so which is more good for creating DCOM components?

prince

in fact, in case of DCOM, either COM objects (DLL and EXE) are essentially running in a seperate process because they reside on a remote machine.
if u want in-proc COM server (i.e. DLL) to run in a separate process (either in the same machine or on remote one) it must be in a DLL surrogate.
this surrogate act as a container for that COM object because in contrast to out-of-process COM server (i.e. EXE), it cannot run on it's own process and must have some process to accommodate it.
if u want to remotely, i reccomend u to use COM+ if u can.
if not, use ActiveX EXE.
COM+ will do the most of the work for u, either in configuration process and at management.
configure DCOM is very cumbersome and painful.
another thing is management, COM+ supply very handy tool to inspect your objects and to handle objects life cycle (like JIT service).
if u working with transaction for instance, u must use COM+.
now, if u don't want to use COM+, ActiveX EXE is simple to use then DLL surrogate.
but watch out, u will encounter quirk things, like memory leak, blocking etc. so, design your EXE server very well before using it.