you could build a bat script to execute the console app. use windows scheduler to schedule when the bat file executes. since this is a console app a user will need to be logged in for the application to execute.
You may also want to consider building this into a windows service. this is better suited for background work.
as for running when not logged in, make sure you dont throw up any messageboxes or anything (like exceptions) that requires user feedback or any type of display. Output your result to a text log or something.
I normally don't like to rely on Scheduled Tasks. I usually implement a Windows Service that uses timer threads. For example, I run a service on an hourly basis and in another instance, I have a thread that runs at exactly midnight to run upload data to Oracle.
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.