Hi Steven,

The default DotNetNuke scheduler implementation utilizes the BuildProvider.GetType(string, bool) method when mapping the schedule type string to underlying type (see the GetSchedulerClient method of the ProcessGroup class located at Providers/SchedulingProviders/DNNScheduler/ProcessGroup.cs).  Because of this, any string that that results in a valid type when passed to this method should work with the scheduler (assuming it also implements the proper interface).

The documentation associated with this method indicates that any assembly-qualified type name is acceptable (as you noted in your original post) along with an unqualified type drawn from one of the App_GlobalResources, App_WebReferences, App_Code, or App_Browsers directories.  If you wish to use a type that cannot be assembly-qualified, it will need to be located there.

An alternate option would be to create a custom scheduling provider.  While DotNetNuke supports this, I would recommend against it unless you are very familiar with asynchronous, thread-oriented development.

Hope this helps!

Brandon 

---

Brandon Haynes
BrandonHaynes.org