It is very dangerous to open forms inside a windows service. You could
lock up the windows service or the server itself.
--
Bryan Phillips
MCSD, MCDBA, MCSE
Blog: http://bphillips76.spaces.live.com
> It is very dangerous to open forms inside a windows service. You
> could lock up the windows service or the server itself.
I'm not sure what are you trying to say.
What is the differenve between windows service with a form and windows
service without a form?
MH
Ciaran O''Donnell - 16 Mar 2007 16:30 GMT
The windows service runs in a logon context which doesnt have an interactive
session to present the form in. Therefore they dont work. If you want a
windows form interface to run in the background then try looking at a
notifyicon instead of a service or potentially as well as.

Signature
Ciaran O''Donnell
http://wannabedeveloper.spaces.live.com
> > It is very dangerous to open forms inside a windows service. You
> > could lock up the windows service or the server itself.
[quoted text clipped - 4 lines]
>
> MH
Bryan Phillips - 16 Mar 2007 21:21 GMT
Basically, never instantiate a Windows Form inside a Windows Service.
Don't use the .Net Print classes inside a Windows Service either.
Ciaran's advice is wise and should be followed.
--
Bryan Phillips
MCSD, MCDBA, MCSE
Blog: http://bphillips76.spaces.live.com
> > It is very dangerous to open forms inside a windows service. You
> > could lock up the windows service or the server itself.
[quoted text clipped - 4 lines]
>
> MH