Error when loading RichTextBox

[Mel]

Greetings, my company is incorporating some of the Telerik controls into our Silverlight application. I have incorporated a RichTextBox, when instantiated I'm am getting the following error

[Line: 0 Position: 0] at MS.Internal.XcpImports.CheckHResult(UInt32 hr) at MS.Internal.XcpImports.SetValue(IManagedPeerBase obj, DependencyProperty property, DependencyObject doh) at System.Windows.DependencyObject.SetValue(DependencyProperty property, DependencyObject doh) at Telerik.Windows.Controls.RichTextBoxUI.MultipleUndoControl.OnActionButtonStyleProperty(DependencyObject o, DependencyPropertyChangedEventArgs args) at Telerik.Windows.PropertyMetadata.PropertyChangeHook.OnPropertyChanged(DependencyObject d, DependencyPropertyChangedEventArgs e) at System.Windows.DependencyObject.RaisePropertyChangeNotifications(DependencyProperty dp, Object oldValue, Object newValue) at System.Windows.DependencyObject.UpdateEffectiveValue(DependencyProperty property, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, ValueOperation operation) at System.Windows.DependencyObject.InvalidateProperty(DependencyProperty property at MS.Internal.FrameworkCallbacks.InvalidateProperty(IntPtr nativeTarget, UInt32 propertyID)

Note, if I 'OK' out of the error box everything seems to work fine.
Thanks
Mel

[Mihail]

Hi Mel,
Can you verify that you have added all needed assembly references?
Looking forward to your reply.

Kind regards,
Mihail
the Telerik team

[Ravi]

add all the references that it need. i have mention all below

xmlns:telerik="http://schemas.telerik.com/2008/xaml/presentation"
    xmlns:telerikWindowsControls="clr-namespace:Telerik.Windows;assembly=Telerik.Windows.Controls"
    xmlns:telerikDocuments="clr-namespace:System;assembly=Telerik.Windows.Documents"
    xmlns:telerikDocumentsUI="clr-namespace:Telerik.Windows.Documents.UI;assembly=Telerik.Windows.Documents"
    xmlns:telerikData="clr-namespace:Telerik.Windows.Data;assembly=Telerik.Windows.Data"
    xmlns:telerikInput="clr-namespace:Telerik.Windows.Controls;assembly=Telerik.Windows.Controls.Input"
    xmlns:telerikRichTextBoxCommands="clr-namespace:Telerik.Windows.Documents.RichTextBoxCommands;assembly=Telerik.Windows.Documents"
    xmlns:telerikRichTextBoxUI="clr-namespace:Telerik.Windows.Controls.RichTextBoxUI;assembly=Telerik.Windows.Controls.RichTextBoxUI"

 

[Iva Toteva]

Hi Ravi,

If all assembly references you have added are:

• Telerik.Windows.Controls;
• Telerik.Windows.Documents;
• Telerik.Windows.Data;
• Telerik.Windows.Controls.Input;
• Telerik.Windows.Controls.RichTextBoxUI,

then you must add reference to the following ones as well:

• Telerik.Windows.Controls.ImageEditor;
• Telerik.Windows.Controls.Input;
• Telerik.Windows.Controls.Navigation;
• Telerik.Windows.Controls.RibbonView.

For import from/ export to different file formats, you would need references to:

• Telerik.Windows.Documents.FormatProviders.OpenXml and Telerik.Windows.Zip for docx;
• Telerik.Windows.Documents.FormatProviders.Html for HTML;
• Telerik.Windows.Documents.FormatProviders.Xaml for XAML;
• Telerik.Windows.Documents.FormatProviders.Rtf for RTF;
• Telerik.Windows.Documents.FormatProviders.Pdf and Telerik.Windows.Zip for PDF (export only).

The default en-US dictionary for SpellChecking is located in:

• Telerik.Windows.Documents.Proofing.Dictionaries.En-US.

Furthermore, the version of all assemblies has to be the same, i.e. if you upgrade a project to the latest version, you have to verify that all references have been successfully updated.

Greetings,
Iva Toteva
the Telerik team

[Mel]

Greetings,
Thanks for your replies!
I have checked the references, they all seem to be there according to your list and the version seems to be the correct one too - Q3 2011. I'm still getting this error though right before the notice that it is a trial version.
Thanks again,
Mel

[Boby]

Hi Mel,
We were not able to reproduce the problem. Please try re-installing the controls and manually delete 'bin' and 'obj' solution folders. If this doesn't help, please open a support ticket and send us attached a sample project that reproduces the exception, so we can investigate it further.

All the best,
Boby
the Telerik team