Out-Of-Process objects and COM+

[kennykjam]

I am trying to add an out-of-process service component to a COM+ application using the Component Services console. The out-of-process service is in the form of an .EXE compiled using C++. Although when I install my application this service is registered and all the registry keys have been set up, the service is not available from the "Import components that are already registered" list.

So I attempted to "Install A New Component" and although the wizard recognises the .EXE as a COM+ compatible component and picks up the typelib and the interface the dialog still does not let me add the component.

The only snippet of info that I can find on the web states:
A COM server, implemented as an .EXE application, which runs outside the process of its client, either on the same machine or a remote machine. Out-of-process server can not be installed into
COM+ Application.

Is this correct ?
IIS after all has it's own out-of-process services installed.

Any help would be much appreciated. I am new to COM+ and am working with a legacy application and MSDN does not have what I'm looking for.

Cheers in advance

[RNEELY]

What version of Visual Studio are you using?

[TheCPUWizard]

A COM+ component can not be an "out of process" component. It must run in the context of the process that COM+ creates for it.

As a result it DOES run "out of process" with respect to the caller/user.


I have been doing all of my COM+ work in C# for about the past two years, so I dont have handy the exact method for setting this up in an unmanaged environemtn, but I am sure someone else will.

[kennykjam]

Microsoft Visual C++ 6.0

[kennykjam]

So a .EXE cannot be added as a component to a COM+ application, period.