Just because Microsoft says that you shouldn’t do something rarely stops developers from trying.

My task was to try to write a Windows Service replacement for a legacy application that saved a Word Document to text and then added headers for shipment to a client’s reporting system.  The legacy system was an old VB6 application that was brittle– not only was there the typical hard coding, but the system must be left in a logged in state because to take it out of that state would mean the system would shut down.

Continue reading

Guy With Laptop

Windows Services are great.  They allow you to write code that will run even when a user is not logged in.  They can perform functions in the background, and they’re very useful.

Writing them, however, is a little more interesting.

If you were to simply open Visual Studio and create a new Windows Services project and start coding, you wouldn’t be able to tell if the code was doing what you wanted without installing it as a service.

Continue reading