I would rather to use Quartz.net, it looks more flexible to me rather than the windows task scheduler but the idea could work for both types of schedulers, Take a look to the following case to get the idea and maybe this helps you out:
- Create a WCF
- Consume the WCF service from your asp-net-mvc application
- the WCF will have methods to perform common operations like add and remove tasks
- Store the information for the task into a persistance storage (db, no-sql, xml, etc) or over your cache
- You must have a JOB (from quartz) that reads the database and creates the tasks into the windows box, this job could run every x minutes or y hours
- Use the information and perform a FIFO operation
- Create a form in your asp-net-app for the users to input the tasks and the form will send the information to your wcf service
Edit:
you need to have the following in mind:
a wcf will give you the state you need to have an "state" to handle the web application tasks, quartz can handle the job to read the database and set up new tasks (quartz or windows scheduler) and the web form is just the front end to handle those operations.
setting up a job in quartz couls be as easy as:
public class ReadDBJob : IJob
{
public void Execute(IJobExecutionContext context)
{
// Do your work to read the database
// and create the tasks that you need
}
}