From: Kim Gräsman (kimMVPS.ORG)
Date: Wed Oct 26 2005 - 11:30:23 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi Peter,

> Only way to do this with CoRegisterClassObject is to load the
> server (just what the original post did not want to allow to happen).

Well, I have no problem with the server starting, I just don't want it
launched by COM activation requests.

> As for the managed code, you can always PInvoke to
> CoCreateInstance so that you can specify the CLSCTX flags,
> and then use the Marshal.CreateWrapperOfType to wrap the
> IntPtr with a RCW of choice. (as an aside, you need to do
> this if attempting to launch in a DLL surrogate for inproc
> servers not configured for COM+)

Thanks, I'll look into that as well. I seem to recall I've changed the
registry key they mention in the docs for CLSCTX_NO_FAILURE_LOG, but that it
didn't help (because it only affects activation and not launch. Figures.)
But specifying it programmatically is easier to test.

Cheers,
- Kim

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.html
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]