Re: Debugging Windows Service
- From: "Dave Sexton" <dave@jwa[remove.this]online.com>
- Date: Sun, 3 Dec 2006 04:16:37 -0500
Hi Derek,
You don't even have to call Launch, just Break, and it shows a nifty little
dialog warning you that your program is in error and may be corrupt,
offering to allow you to debug it.
But I'm not sure if it'll work in a Windows Service.
Just thought you might like to know :)
--
Dave Sexton
"Derek Hart" <derekmhart@xxxxxxxxx> wrote in message
news:uX79SWlFHHA.5104@xxxxxxxxxxxxxxxxxxxxxxx
As a newbie to Windows Service programming in VB.Net, I need some
clarification. I am writing a Windows Service that works with SQL Server.
It works fine as a console application, but when I run it as a service it
is having problems. I want to be able to debug it, so I placed this code
in the OnStart routine which allows me to break into the code:
System.Diagnostics.Debugger.Launch()
System.Diagnostics.Debugger.Break()
It looks like the only way I am allowed to debug the process is setting
the logon in the service (once it is installed of course) to the Local
System Account and choosing "Allow service to interact with desktop." But
it looks as if Local System does not have access to SQL Server, as I am
getting an "Unable To Connect To Server" error. Should Local System have
access?
Derek
.
- References:
- Debugging Windows Service
- From: Derek Hart
- Debugging Windows Service
- Prev by Date: Re: Suggest where I could get a Software License Agreement
- Next by Date: Re: Convert asp.net user control to windows app?
- Previous by thread: Re: Debugging Windows Service
- Next by thread: Re: Search a folder with .doc, .xls
- Index(es):
Relevant Pages
|
