For those using Telerik’s RadScheduler control, I explained about the options that the scheduler uses to recur by:  http://dotnetslackers.com/articles/aspnet/Understanding-Teleriks-Scheduler-Recurrence.aspx  I don’t know if the latest release has changed some of these settings, but this article was up to date as of the previous 2008.3 release.  The scheduler uses a unique convention to identify recurring appointments within the scheduler control, and I give an overview of the various features.  Once you have an understanding of these features, using the scheduler control becomes easier.

For instance, one of the weird things about the control is how it keeps track of modifications to recurring appointments.  The recurrence string stores a list of excluded dates; these dates block appointments from showing on the calendar.  In addition, the API for the scheduler creates a new entry for modified instances of the recurring appointment (when changing a single instance within the scheduler).  I hope this article can help you understand the recurrence features the scheduler provides.

I also provide an overview of the control here:  http://dotnetslackers.com/articles/aspnet/Using-Teleriks-Scheduler-Component.aspx