Installing a .net windows service

[rockdady]

I have recently built a .net windows service. This is a very simple
service that fires off a web service at a scheduled time. I then
created a setup using the following microsoft guidelines.

http://msdn.microsoft.com/library/de...pplication.asp

I then ran the setup. The service never shows up in my list of
services.

Has anyone else run in to this problem or resolved this type of problem

Thanks in advance for any help or advice

[Al Reid]

"rockdady" <ro******@sbcglobal.net> wrote in message
news:11*********************@g14g2000cwa.googlegro ups.com...

I have recently built a .net windows service. This is a very simple
service that fires off a web service at a scheduled time. I then
created a setup using the following microsoft guidelines.

http://msdn.microsoft.com/library/de...pplication.asp

I then ran the setup. The service never shows up in my list of
services.

Has anyone else run in to this problem or resolved this type of problem

Thanks in advance for any help or advice

You need to run "Installutil.exe servicename.exe" to install the service.
Then you can configure the service launching the Administrative Tools ->
Services app.

--
Al Reid

[CMM]

This doesn't answer your question but I just wanted to comment: Anything
that involves "scheduling" is best done IMO with Window's built-in Task
Scheduler... which many people don't realize doesn't need a logged-on user
to run and allows you to execute a program using specific credentials
exactly as if the program were a service. A lot of folks including
commercial ISV's seem to want to reinvent this wheel.

[VayTek]

Be sure your scheduled task doesn't expect to interact with a windows form or
UI in some way or another. You can generally get away with a console
interface that dumps data to stdout or stderr by redirecting the output to a
file but a windows app may not work at all or may work intermittently and
fail intermittently.

For instance if the program is primarily a batch operation written in vb but
it has some left over form window this may cause problems when running as a
background task even if the form isn't referenced.
--
VayTek Programmer
"CMM" wrote:

This doesn't answer your question but I just wanted to comment: Anything
that involves "scheduling" is best done IMO with Window's built-in Task
Scheduler... which many people don't realize doesn't need a logged-on user
to run and allows you to execute a program using specific credentials
exactly as if the program were a service. A lot of folks including
commercial ISV's seem to want to reinvent this wheel.