Hi there,

    I've got a dll I'm using in an ASP page of mine that I would like to
fire off using a surrogate process.  I know IIS has the "run in separate
memory space" option you can choose for virutal directories, but for various
reasons, I can't use that here.

    Instead, I've used the OLE/COM viewer application to change my dll's
various classes to use a surrogate process (using the checkbox).  The
trouble is, nothing seems to happen differently than before; that is to say,
when my dll is used in my web page, no additional copies of dllhost.exe are
fired up, but instead, my components are fired up with inetinfo.exe, just
like always.

    I can't figure out why the checkbox isn't working for me, and wondered
if anyone had any ideas out there as to what I'm doing wrong.  Thanks very
much for your input and advice.

I have never seen the "surrogate process" checkbox you speak of, but my
involvement with custom components is only that of the admin of the system
upon which it resides; however, I'm compelled to at least respond when this
thread seems to have gone unnoticed.

First, why exactly can you NOT use a higher level of application protection
as provided by IIS?  Yes, it will result in lower system performance, but
just curious

Now, on to real questions..
Does the application work as expected right now?  How exactly do you have
these components installed?  Have you created an empty COM application and
registered the dlls within the app?  If so, is the application being
executed under the context of the logged on user or as a predefined role
account?

In my current environment, we have two separate applications consisting of
28 and 14 components.  Upon the initial firing of the site, we have two
additional dllhost.exe process appear like clockwork...  hopefully (though
I'm not that great of a developer) I can help you achieve the same results.

verbal
http://www.mrverbal.com