As mentioned in my earlier post regarding creating an application
object from a Windows service, I have a Windows app that I'm migrating
to a Windows service. This is the first time I have written a Windows
service, and it has been pretty difficult. What I'm wondering is,
should my application be a Windows Service. Here's a description of the
functionality:
Another program sends messages to MSMQ notifying that some document
properties have been changed. My application must poll MSMQ and read
all of those messages. There is a message for each document property
change. If that change is the one I want to react to, my app must open
a 3rd program, the native editor for those files, which supports
automation via VB, and do some processing on the files. Then it
generates a log file.
I can make this work with a user logged on and using the system account
with interact with desktop turned on using normal CreateObject( ,
"App") call. But it doesnt work in a logged off state (because there is
no desktop to interact with?)
Does this sound like I should be using a Windows Service? I dont care
if the user can see the applications run if there is a user logged on.
I only care that the processing is done correctly.
Thanks.
- Luther
