best practices when creating testing and deploying windows services ?

Question

i building a small windows service (not a web service) that periodically check for some data and based on that and call a class library to do some work

BTW: this is the first time i try to create a windows service

Answer 1

There's some of stuff here, walk throughs architecture, etc. I guess the biggest mistake I see people making when they write a windows service is to try and somehow interact with the desktop or the user. Don't do that. :)

Answer 2

Check out this link.

Answer 3

Windows services are by definition hard to test because you must always install them and uninstall them every time when you change something.

It is best to decouple BL that you writing for service and put it in a separate class. After that you can write simple win desktop application where you will use and test this BL class. After you finished testing it is easy to include same logic to a Windows Service project.

For debugging Windows Service you have to Attach to process and after that it is very easy to test code directly.

Hope that this will help...