The easiest option would be to have a command line switch.  Setup your scheduled task to launch your program like so:

    myProgram.exe /noui

Then just use Environment.GetCommandLineArgs() to check for the flag.  If it exists, don't show your UI.

This way, when the user just starts your program normally, it'll run with a UI.  When you schedule the task, as long as you put in the flag, it won't show the UI.

A more elaborate, but potentially nicer approach, would be to make 2 versions of your program.  Move all of your logic to a library project (DLL), and just have a exe that wraps the DLL in a UI, and an exe that wraps it in a console app.  Use the console app for your scheduled task.

---

Reed Copsey, Jr. - http://reedcopsey.com

Reed,

Thanks for the update. I already have a commandline option that sends the name of a file which determines how to run the application (RunMode - Service or Normal). The problem is sometimes users dont setup the correct value and try to run the Normal mode as service mode. I wanted to see if I can detect such things and inform the user.

Difficult to test it in all cases.  You could, potentially, try to check to see what user you're running under, and adjust accordingly, but that's prone to error, since it's possible to run a task as a user, etc.

If you're already doing this, and it's not working well enough for you, I'd suggest my second option above - move the logic to a DLL (pretty much everything except your program entry point), and have 2 executables - a UI version and a task version.  That should make it much more obvious to your users.

---

Reed Copsey, Jr. - http://reedcopsey.com

Reed,

Thanks. I'll see if that helps.