HOWTO: Configure a DLL Surrogate for Use with ASPID: Q194023
|
This article explains how to configure the registry to use in-process
components outside the main process either on the same machine or on a
remote server.
IMPORTANT: This article contains information about editing the registry.
Before you edit the registry, make sure you understand how to restore it if
a problem occurs. For information about how to do this, view the "Restoring
the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key"
Help topic in Regedt32.exe.
DCOM provides a default DLL surrogate (Dllhost.exe) that can act as a host for your in-process components. The file Dllhost.exe is an executable component that you can run remotely and instruct to load any in-process component, providing the component with a surrogate parent process and security context.
REGEDIT4
[HKEY_CLASSES_ROOT\CLSID\{10000002-0000-0000-0000-000000000001}]
"AppID"="{10000002-0000-0000-0000-000000000001}"
[HKEY_CLASSES_ROOT\AppID\{10000002-0000-0000-0000-000000000001}]
@="Surrogate DLL Sample"
"DllSurrogate"=""
Since no surrogate name is provided in this case, the system-supplied
surrogate, Dllhost.exe, will be used by default.
REGEDIT4
[HKEY_CLASSES_ROOT\CLSID\{10000002-0000-0000-0000-000000000001}]
"AppID"="{10000002-0000-0000-0000-000000000001}"
[HKEY_CLASSES_ROOT\AppID\{10000002-0000-0000-0000-000000000001}]
@="Surrogate DLL Sample"
"RemoteServerName"="Remote_Computer_Name"
These entries specify whenever a client comes looking for the component,
the component should actually be run on another machine specified by the
RemoteServerName value.
Additional query words:
Keywords : kbASP kbCOMt kbDCOM kbWebServer kbGrpASP
Version : WINDOWS:6.0; winnt:
Platform : WINDOWS winnt
Issue type : kbhowto
Last Reviewed: May 27, 1999