Hello Nader,
> A simple question, I might have something wrong with my concepts, so
> point it to me. Please this is important so if you have any lead just
> send it along.
>
> Can we expose COM+ object out-process?
Yes.
> Can we do that using .NET?
Yes.
> How if possible, and why if not?
If you configure the COM+ application as "Server Application" (see
Activation tab)
Pierre

Signature
-------------------------------------------
Pierre Greborio
Microsoft .NET MVP
http://blogs.ugidotnet.org/pierregreborio
http://www.amazon.com/infopath
-------------------------------------------
nadersoliman@gmail.com - 02 Mar 2005 20:08 GMT
Thanks Pierre for the reply ...
But when we configure COM+ application as "Server Application" COM+
uses its own surrogate ... I don't remeber but I guess dllhost.exe
right?
What I meant can we expose that very COM+ from our out-process
application, our surrogate.
Simply the situation is that I am forced to use remoting to communicate
between COM+ object and a service, the object does nothing but forward
the call through remoting to the service.
I wondered, why shouldn't I expose that COM+ object from the service,
so they exists in the same AppDomain and I won't need remoting at all?
I am missing something here ... or is there a concept wrong?
Tanks in advance,
Nader
Chee Pin Cheam - 16 Mar 2005 18:21 GMT
> Thanks Pierre for the reply ...
>
[quoted text clipped - 16 lines]
> Tanks in advance,
> Nader
Nader,
Yes, when you configure serviced component as server application, it
will be hosted by dllhost.exe. Essentially, when your .net client is
calling the server based serviced component, it looks as if it is over
remoting, in real fact, it does DCOM on the wire.
Chee Pin