debugging a service

[Harry Hudini]

How on earth are you meant to debug a service in .net ? Clearly it wont let
me debug the service from the IDE, but running the service as a service on a
machine severely limits what you can do. debuggin by using the event log is
impossible.

Any ideas on how to best approach this ?

Olly

--
________________________________________________
ADSSupport.net
http://www.adssupport.net
Dedicated free Active Directory ServicesT support

email: oliver.marshall@no****@adssupport.net

[Fergus Cooney]

Hi Harry,

What do you mean impossible to use the Event Log? All you have to do is
keep a clunky MMC open, play with a waste of space foilder view, keep opening
and closing messages? Keep clearing down the log and 'yes, I'm sure, already'.
What more do you want?

At its worst, using the file system will be easier than the Event Log.
Leave that for going live. Just don't forget to keep flushing that debug file.

A better approach, perhaps: Is there anything particularly 'servicey'
about what your servioce does or is it an app that you just want to run as a
service?

If it's the latter, simply don't install it as a service. Write a GUI that
is separate and uses the service logic to do its thing. Then, when satisifed,
rebuild that same logic inside a Service framework.

If it's the former, you can use the same approach but write spoof servicey
stuff which will give your service correct values of your own choosing. Then,
as before, whack it back into a true service.

Regards,
Fergus

[Harry Hudini]

THanks Fergus,

Im convertng some vb6 apps to .net and thought i would use this as a chance
to convert some things to services with the new service feature of .net.

THink im gonna go shove hot pokers into my eyes instead.

Olly

"Fergus Cooney" <fi****@post.com> wrote in message
news:OV*************@TK2MSFTNGP09.phx.gbl...

Hi Harry,

What do you mean impossible to use the Event Log? All you have to do is keep a clunky MMC open, play with a waste of space foilder view, keep opening and closing messages? Keep clearing down the log and 'yes, I'm sure, already'. What more do you want?

At its worst, using the file system will be easier than the Event Log.
Leave that for going live. Just don't forget to keep flushing that debug file.
A better approach, perhaps: Is there anything particularly 'servicey'
about what your servioce does or is it an app that you just want to run as a service?

If it's the latter, simply don't install it as a service. Write a GUI that is separate and uses the service logic to do its thing. Then, when satisifed, rebuild that same logic inside a Service framework.

If it's the former, you can use the same approach but write spoof servicey stuff which will give your service correct values of your own choosing. Then, as before, whack it back into a true service.

Regards,
Fergus

[Fergus Cooney]

Hi Olly,

ROFLMAO.

Well, when you're done, come here and we'll rub some cream (gently) into
them. It's been claimed that we're not a hospital here, but we can be good for
body, mind and soul, not to mention console.

I'd definitely recommend the VB6 App -> VB.NET App -> VB.NET Win Service
approach. The first stage will give you far more problems (ahem, challenges)
than the second stage.

Good luck. ;-)

Regards,
Fergus