Re: Make a Windows Service start a windows program.
- From: "deko" <deko@xxxxxxxxxx>
- Date: Wed, 22 Feb 2006 09:50:02 -0800
The OP's question relates to a "windows" program, not a console style
program. Note that the same remark about the user profile applies when
starting a console application, an application that considers it's profile
being loaded when started will fail if started from a service.
In general, services should not start other applications, unless you have
full control of it's UI and profile context.
What do you mean when you say:
"unless you have full control of it's UI and profile context"?
I have a similar situation where a service needs to instantiate an object contained in a WinForms app. The service and the app are installed as a pair; the UI is used to define the action taken by the service at pre-defined intervals.
When constructing the assembly in Visual Studio that contains the application/service pair, should the service and the app be in a separate namespaces? Does it make any difference? The design goal is to keep the service and the app a loosely coupled as possible since they run in different security contexts.
.
- Follow-Ups:
- Re: Make a Windows Service start a windows program.
- From: Willy Denoyette [MVP]
- Re: Make a Windows Service start a windows program.
- References:
- Make a Windows Service start a windows program.
- From: UJ
- Re: Make a Windows Service start a windows program.
- From: Willy Denoyette [MVP]
- Re: Make a Windows Service start a windows program.
- From: KBuser
- Re: Make a Windows Service start a windows program.
- From: Willy Denoyette [MVP]
- Make a Windows Service start a windows program.
- Prev by Date: Re: crossthreading issue
- Next by Date: Re: Make a Windows Service start a windows program.
- Previous by thread: Re: Make a Windows Service start a windows program.
- Next by thread: Re: Make a Windows Service start a windows program.
- Index(es):
Relevant Pages
|
Loading