As mentioned earlier we will do our best to fix the described issue with the GetOccurrences method in the RadScheduleView control. Unfortunately as all of our tasks for the next official release have been planned we cannot estimate if this issue will be resolved in that release. We will do our best to have a permanent fix for it as soon as possible.
In the meanwhile you could easily filter the returned collection by the GetOccurrences method in order to exclude such "incorrect" exception occurrences. The next code snippet shows how to manually filter that collection:
and it the code:
sender, RoutedEventArgs e)
var appointments =
var start =
DateTime(2014, 7, 1);
var end =
DateTime(2014, 7, 10);
var result = appointments.GetOccurrences(start, end).Where(o => o.IntersectsWith(
IDateSpan source, IDateSpan other)
&& other !=
((other.Start <= source.Start && source.Start < other.End) ||
(source.Start <= other.Start && other.Start < source.End));
I updated your Telerik points for bringing this to our attention. We apologize for any inconvenience that this may be causing.
Check out Telerik Analytics, the service which allows developers to discover app usage patterns, analyze user data, log exceptions, solve problems and profile application performance at run time. Watch the videos
and start improving your app based on facts, not hunches.