🚀 go-pugleaf

Hi Gambit



Mmmh... not the answer I expected, but thanks anyway.

I guess I tried to take a short cut and avoid having to have two 
applications and communicate through IPC.



Rds

Marc


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> schrieb im Newsbeitrag 
news:4720cb19$1@newsgroups.borland.com...
>
> "Marc" <info@mawnet.com> wrote in message 
> news:4720c4bf@newsgroups.borland.com...
>
>> Now I create a blank form and display [MyForm->Show()]
>> it in the ServiceStart event.
>
> DO NOT EVER display a UI from a service!!!  Services are background 
> processes.  They are not supposed to interact with the user directly, with 
> the exception of simply MessageBox() dialogs when notifications are 
> needed. In fact, UIs in services are strictly not allowed anymore starting 
> with Vista.  For a service to display a UI, the proper way to handle that 
> (in any OS version) is to create a separate non-service application that 
> runs after the user has logged in, and then have that application 
> communicate with the service as needed using any of a number of IPC 
> (inter-process communication) technologies that are available, such as 
> sockets or named pipes.
>
>> If I check with the debugger, it crashes when it tries to release my form 
>> at the end of the application.
>
> Another reason not to use UIs in services - TService is multi-threaded, 
> and the VCL's UI components are not thread-safe.
>
>> I have written services before that open Forms in the OnExecute loop.
>
> You should never have been doing that in the first place.
>
>
> Gambit
>