This problem is caused by a limitation in the Silverlight XAML parser, which sometimes fails to recognize the types of the XAML elements - this particular exception occurs when you first visit a RadScheduleView example, then open RadScheduler example. Since the assemblies of those controls contain classes with the same name, the XAML parser tries to set properties on types from the RadScheduleView assembly that are not present. In normal applications you would usually use only one of the controls, hence the problem should not exist. If you need to use both controls, you will have to declare the XML namespaces with the full CLR-namespace/assembly syntax instead of the URI namespace.
the Telerik team
Registration for Q1 2011 What’s New Webinar Week is now open. Mark your calendar for the week starting March 21st and book your seat
for a walk through all the exciting stuff we ship with the new release!