the is going to run as a windows service and it will continually keep track of the values of certain controls and then send out emails everyday with a status report.
That's fine. Using Sheduled Tasks is still the proper way of accomplishing this task.
Code:
application.exe /report
Run your application with a similar command line, which in turn notifies the currently running service to generate a report. You can communicate between the two instances of your application using Windows Sockets which is the method used by Microsoft and other vendors.
Then again, if you choose not to use Scheduled Tasks, you'll be forced into polling the system time, which I believe is what you were trying to get away from.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.