I'm using Scheduler - it works just fine on timed tasks.  I've been wrestling trying to get a simple task to start based on the Application_Start event.  The best that happens is that in the Schedule list the 'Next Start' time gets set to when the application starts - but the code never runs.    (I've tested it by setting a time lapse - and then it runs fine...)

The parameters I use to set this up are:

• Full Class Name: RSL.RSLStartup (again, works with a time lapse)
• Schedule enabled: true
• Time lapse: left blank
• Retry frequency: left blank
• Retain schedule history: None (I've tried 25 as well)
• Run on event: APPLICATION_START
• Catch up enabled: not checked
• Object dependencies: none
• Run on servers: none

The code is (in namespace RSL)

public class RSLStartup : DotNetNuke.Services.Scheduling.SchedulerClient
{
 
{
ScheduleHistoryItem = objScheduleHistoryItem;
}
 
 
{
 
}
}public RSLStartup(DotNetNuke.Services.Scheduling.ScheduleHistoryItem objScheduleHistoryItem) : base()public override void DoWork()try
{
Progressing();
RSL.
ScheduleHistoryItem.Succeeded = 
ScheduleHistoryItem.AddLogNote(
}
 
{
ScheduleHistoryItem.Succeeded = 
ScheduleHistoryItem.AddLogNote(
Errored(
}RSLBase.vInitialize();true;"Startup");catch (Exception err)false;"Startup EXCEPTION: " + err.Message);ref err);

If the scheduler mode is set to Timer, and you have a task which is assigned to run on Application_Start, this will crash DNN on the next app restart and it will never load. I found this in testing and it is known in the core. If the scheduler mode was set to Request (which it is by default) this shouldn't be a problem. After some discussions w/ Shaun, I don't really see a reason you need to assign a task to Application_Start for 99% of use cases.