Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / Component Services / March 2005

Tip: Looking for answers? Try searching our database.

Question Rephrase : Outprocess COM+ using .NET?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
nadersoliman@gmail.com - 01 Mar 2005 18:51 GMT
Hi Everyone,

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?

Can we do that using .NET?

How if possible, and why if not?

Best Regards,
Nader Soliman
Pierre Greborio - 02 Mar 2005 07:52 GMT
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

Rate this thread:







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 ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.