Scheduler - Hi level description?

Last post 03-03-2005 11:52 AM by CelebesCoder. 3 replies.

Sort Posts:

  • Scheduler - Hi level description?

    03-02-2005, 11:44 AM
    • Contributor
      6,080 point Contributor
    • rodneyjoyce
    • Member since 10-24-2002, 3:45 AM
    • London
    • Posts 1,216
    Hi

    I host at home and am considering moving to a hosting service (my server is so full of backdoors and viruses I've just given up ;) - anyway, I have a windows service that polls my user data and emails users on their birthdays - I am not really familiar with the Scheduler functionality, but obviously if I went to a hosting provider they would not allow me to install my service - is this something that I could do with scheduler (ie. run some business logic).
    Rodney

  • Re: Scheduler - Hi level description?

    03-02-2005, 12:54 PM
    • Contributor
      4,805 point Contributor
    • lucast
    • Member since 07-30-2002, 4:32 PM
    • Texas
    • Posts 961
    Sure. It really is simply a wrapper that allows the DNN scheduler to call you class(es) and execute some business logic on a recurring basis. Take a look at the /components/log/PurgeSiteLog.vb example.

    Basically create a class that inherits from DotNetNuke.Services.Scheduling.SchedulerClient. Then you have a DoWork Sub that overrides the base class. In this routine, call you other subs with your business logic.

    Pretty simple really, but it takes a few minutes to get your arms around it.

    HTH
    Tom Lucas

  • Re: Scheduler - Hi level description?

    03-02-2005, 6:46 PM
    • Contributor
      6,080 point Contributor
    • rodneyjoyce
    • Member since 10-24-2002, 3:45 AM
    • London
    • Posts 1,216
    aaah-- Tom to the rescue (again!)

    Thanks - I'll add that to my today list - just what I needed!
    Rodney

  • Re: Scheduler - Hi level description?

    03-03-2005, 11:46 AM
    • Member
      115 point Member
    • CelebesCoder
    • Member since 05-24-2004, 12:02 PM
    • Connecticut
    • Posts 29
    One thing to be aware of: because the Scheduler process is running out of process, you won't be able reference HttpContext.Current.

    I ran into this problem when creating a process to run on Scheduler. The scheduler could not start because of this.

    HTH
    Ricky.
Page 1 of 1 (4 items)