Scott Lavender
Top achievements
Rank 1
Rank 1
Scott Lavender
asked on 16 Nov 2009, 05:07 PM
After upgrading to the Q3 09 silverlight libraries we started encountering the following runtime error on a page that contains a RadCoverFlow.
Message = "Cannot resolve TargetName DisabledBox."
+ ExceptionObject {System.InvalidOperationException: Cannot resolve TargetName DisabledBox.
at MS.Internal.XcpImports.VisualStateManager_GoToState(Control reference, String StateName, Boolean useTransitions)
at System.Windows.VisualStateManager.GoToState(Control control, String stateName, Boolean useTransitions)
at System.Windows.Controls.Control.GoToState(Boolean useTransitions, String stateName)
at System.Windows.Controls.ListBoxItem.ChangeVisualState(Boolean useTransitions)
at System.Windows.Controls.ListBoxItem.ChangeVisualState()
at System.Windows.Controls.ListBoxItem.OnIsEnabledChanged(IsEnabledChangedEventArgs e)
at System.Windows.Controls.Control.OnIsEnabledChanged(Control control, EventArgs args)
at MS.Internal.JoltHelper.FireEvent(IntPtr unmanagedObj, IntPtr unmanagedObjArgs, Int32 argsTypeIndex, String eventName)} System.Exception {System.InvalidOperationException}
Our code doesn't explicitly define a target named DisabledBox. Has anyone else seen this error or have any insight as to what might be causing this problem after upgrading to the new telerik release?
StackTrace " at MS.Internal.XcpImports.VisualStateManager_GoToState(Control reference, String StateName, Boolean useTransitions)\r\n at System.Windows.VisualStateManager.GoToState(Control control, String stateName, Boolean useTransitions)\r\n at System.Windows.Controls.Control.GoToState(Boolean useTransitions, String stateName)\r\n at System.Windows.Controls.ListBoxItem.ChangeVisualState(Boolean useTransitions)\r\n at System.Windows.Controls.ListBoxItem.ChangeVisualState()\r\n at System.Windows.Controls.ListBoxItem.OnIsEnabledChanged(IsEnabledChangedEventArgs e)\r\n at System.Windows.Controls.Control.OnIsEnabledChanged(Control control, EventArgs args)\r\n at MS.Internal.JoltHelper.FireEvent(IntPtr unmanagedObj, IntPtr unmanagedObjArgs, Int32 argsTypeIndex, String eventName)" string
Message = "Cannot resolve TargetName DisabledBox."
+ ExceptionObject {System.InvalidOperationException: Cannot resolve TargetName DisabledBox.
at MS.Internal.XcpImports.VisualStateManager_GoToState(Control reference, String StateName, Boolean useTransitions)
at System.Windows.VisualStateManager.GoToState(Control control, String stateName, Boolean useTransitions)
at System.Windows.Controls.Control.GoToState(Boolean useTransitions, String stateName)
at System.Windows.Controls.ListBoxItem.ChangeVisualState(Boolean useTransitions)
at System.Windows.Controls.ListBoxItem.ChangeVisualState()
at System.Windows.Controls.ListBoxItem.OnIsEnabledChanged(IsEnabledChangedEventArgs e)
at System.Windows.Controls.Control.OnIsEnabledChanged(Control control, EventArgs args)
at MS.Internal.JoltHelper.FireEvent(IntPtr unmanagedObj, IntPtr unmanagedObjArgs, Int32 argsTypeIndex, String eventName)} System.Exception {System.InvalidOperationException}
Our code doesn't explicitly define a target named DisabledBox. Has anyone else seen this error or have any insight as to what might be causing this problem after upgrading to the new telerik release?
StackTrace " at MS.Internal.XcpImports.VisualStateManager_GoToState(Control reference, String StateName, Boolean useTransitions)\r\n at System.Windows.VisualStateManager.GoToState(Control control, String stateName, Boolean useTransitions)\r\n at System.Windows.Controls.Control.GoToState(Boolean useTransitions, String stateName)\r\n at System.Windows.Controls.ListBoxItem.ChangeVisualState(Boolean useTransitions)\r\n at System.Windows.Controls.ListBoxItem.ChangeVisualState()\r\n at System.Windows.Controls.ListBoxItem.OnIsEnabledChanged(IsEnabledChangedEventArgs e)\r\n at System.Windows.Controls.Control.OnIsEnabledChanged(Control control, EventArgs args)\r\n at MS.Internal.JoltHelper.FireEvent(IntPtr unmanagedObj, IntPtr unmanagedObjArgs, Int32 argsTypeIndex, String eventName)" string
1 Answer, 1 is accepted
0
Accepted
Hi Scott Lavender,
Yes, we are aware of this problem and we have already resolved it. The problem comes from an incorrect target name in our Disabled visual state. You can either experience this problem if you explicitly disable any of the CoverFlowItems, or you use ChildWindow control, when opened, disables all controls in the current application. To get rid of the problem download our latest internal build in Friday that will contain the fix. Until then please excuse us for it, and we hope this won't be a showstopper for you.
If you have any other concerns, please feel free to contact us again.
Best wishes,
Hristo Borisov
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Yes, we are aware of this problem and we have already resolved it. The problem comes from an incorrect target name in our Disabled visual state. You can either experience this problem if you explicitly disable any of the CoverFlowItems, or you use ChildWindow control, when opened, disables all controls in the current application. To get rid of the problem download our latest internal build in Friday that will contain the fix. Until then please excuse us for it, and we hope this won't be a showstopper for you.
If you have any other concerns, please feel free to contact us again.
Best wishes,
Hristo Borisov
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.