Archive of UserLand's first discussion group, started October 5, 1998.

Re: Visible Windows-based HTTP apps

Author:Jim Roepcke
Posted:12/13/1998; 2:55:38 PM
Topic:Visible Windows-based HTTP apps
Msg #:1157 (In response to 1153)
Prev/Next:1156 / 1158

I think the problem is that your IIS dll is referencing/instancing the Frontier COM server directly, and it runs it under a security context (LocalSystem ?) that doesn't show the UI.

I think a solution would be to stick another com object inbetween the frontier iis dll and frontier. Your dll would create an instance of the new type, and that object would talk to Frontier via COM. It should be possible for your intermediate object to talk to Frontier while it's UI is up.

It would check it Frontier is running. If it wasn't it would launch it, rather than instancing right away, so that the UI would be visible. If Frontier was running, it would just connect right away.

Don't forget about this page:

http://www.microsoft.com/workshop/server/components/outproc.asp

There are responses to this message:

This page was archived on 6/13/2001; 4:46:30 PM.

© Copyright 1998-2001 UserLand Software, Inc.