L
Lance Colton
it only behaves as expected if i edit the service to run under the system
account and enable the "allow service to interact with desktop" option. if i
run without that enabled or run it under my currently logged on account it
gives an error saying the service started and then stopped right away. i
just created a new vb.net service and put a timer in it and set the interval
and put some code in the Timer1_Elapsed... the timer is just the default
one of type system.timers.timer , is there another type i should be using
here?
also how come when i hit the debug button it tells me you cannot start the
service from the command line or debugger, and if i wait a few seconds
before hitting ok my timer event fires and i can debug it fine?? is there
some other way to debug it properly?
thanks in advance
account and enable the "allow service to interact with desktop" option. if i
run without that enabled or run it under my currently logged on account it
gives an error saying the service started and then stopped right away. i
just created a new vb.net service and put a timer in it and set the interval
and put some code in the Timer1_Elapsed... the timer is just the default
one of type system.timers.timer , is there another type i should be using
here?
also how come when i hit the debug button it tells me you cannot start the
service from the command line or debugger, and if i wait a few seconds
before hitting ok my timer event fires and i can debug it fine?? is there
some other way to debug it properly?
thanks in advance