I am using Q2 2010 Silverlight controls with Silverlight 4.
I changed my xmlns declarations from the following old style:
xmlns:telerik="clr-namespace:Telerik.Windows.Controls;assembly=Telerik.Windows.Controls"
xmlns:telerikInput="clr-namespace:Telerik.Windows.Controls;assembly=Telerik.Windows.Controls.Input"
xmlns:telerikTransitions="clr-namespace:Telerik.Windows.Controls.TransitionEffects;assembly=Telerik.Windows.Controls"
and replaced those three declarations with a single simpler Silverlight 4 style:
xmlns:telerik="http://schemas.telerik.com/2008/xaml/presentation"
This allows you to change the declaration for the transition from this:
Unfortunately, at least for the FadeTransition (does not happen for all the transitions) this results in the following error:
Error 69 Ambiguous type reference. A type named 'FadeTransition' occurs in at least two namespaces, 'Telerik.Windows.Controls' and 'Telerik.Windows.Controls.TransitionEffects'. Consider adjusting the assembly XmlnsDefinition attributes.
Please research this problem.
I changed my xmlns declarations from the following old style:
xmlns:telerik="clr-namespace:Telerik.Windows.Controls;assembly=Telerik.Windows.Controls"
xmlns:telerikInput="clr-namespace:Telerik.Windows.Controls;assembly=Telerik.Windows.Controls.Input"
xmlns:telerikTransitions="clr-namespace:Telerik.Windows.Controls.TransitionEffects;assembly=Telerik.Windows.Controls"
and replaced those three declarations with a single simpler Silverlight 4 style:
xmlns:telerik="http://schemas.telerik.com/2008/xaml/presentation"
This allows you to change the declaration for the transition from this:
<telerikTransitions:FadeTransition>
</telerikTransitions:FadeTransition>
to this:
<telerik:FadeTransition>
</telerik:FadeTransition>
Unfortunately, at least for the FadeTransition (does not happen for all the transitions) this results in the following error:
Error 69 Ambiguous type reference. A type named 'FadeTransition' occurs in at least two namespaces, 'Telerik.Windows.Controls' and 'Telerik.Windows.Controls.TransitionEffects'. Consider adjusting the assembly XmlnsDefinition attributes.
Please research this problem.