Re: Windows Shell Extensions - Out of Proc

Thomas Heller wrote: Ralf schrieb: I think that for whatever reasons, explorer always tries to create shell extensions as InProc. CoCreateInstance, which is the usual API to create COM instances, allows to specify which one you want. Thomas So there is no way to do this, other than to create

Re: Windows Shell Extensions - Out of Proc

Ralf schrieb: >> I think that for whatever reasons, explorer always tries to create >> shell extensions as InProc. CoCreateInstance, which is the usual >> API to create COM instances, allows to specify which one you want. >> >> Thomas > > So there is no way to do this, other than to create a "pro

Re: Windows Shell Extensions - Out of Proc

> I think that for whatever reasons, explorer always tries to create > shell extensions as InProc.  CoCreateInstance, which is the usual > API to create COM instances, allows to specify which one you want. > > Thomas So there is no way to do this, other than to create a "proxy" COM object as InPr

Re: Windows Shell Extensions - Out of Proc

Ralf schrieb: > I'm trying to develop Windows Shell Extensions with the Python Win32 > Extensions. Most of the samples are working. However, I have a > slightly different need: I want the Python COM server to run as a > separate process ("LocalServer" or "OutOfProc"). > > As I understand, both the

Windows Shell Extensions - Out of Proc

I'm trying to develop Windows Shell Extensions with the Python Win32 Extensions. Most of the samples are working. However, I have a slightly different need: I want the Python COM server to run as a separate process ("LocalServer" or "OutOfProc"). As I understand, both the InProc and LocalServer ve