With the current builds 2017.2.614 (and potentially previous one) we are getting a consistent error in the designer:
Error: Unhandled Error in Silverlight Application Cannot find a Resource with the Name/Key thumbResizeMargin [Line: 26 Position: 49]
In production it occasionally takes down our entire product with the white screen of death when rendering the control.
There is an entry in the feedback forums but it doesn't suggest a timely fix. Link
Is there a quick fix or property we can set to avoid this issue? We really cannot wait until the next service pack to address this. Please advise.
7 Answers, 1 is accepted
Just tested previous DLLs
Issue occurs in:
Does not in:
Stated as fixed on Internal Release 2017.2.619, but we can't goto production with this DLL. Is there anything else we can do?
Thank you for opening the ticket.
I already answered in the support thread but will post a reply here as well in case anyone else encounters this question.
Indeed, the design time error with message "Cannot find a Resource with the Name/Key thumbResizeMargin" is already fixed and the fix is included in our Latest Internal Build. Unfortunately, we didn't manage to find a workaround for the error for the current official version.
Thank you Tanya. I cannot reproduce the issue during runtime with 2017.2.619+. I, more than once, observed this as a script debugging error in IE, which took down our entire app. It was difficult to reproduce but the error was "Cannot find a Resource with the Name/Key thumbResizeMargin", so that designer issue somehow made it to runtime.
Is it possible to get a release build of 2017.2.619 so we may repackage and push a fix?
I am happy to hear that the runtime error is not reproducible after the fix.
We are currently working on the tasks for the next official version of the controls and pushing a release build at this point is not possible. I sent you a detailed reply the support ticket and would suggest you to continue our conversation there so we can keep it consistent. Thank you for understanding.
FYI to all:
After testing the runtime issue is still there.
1. RichTextBox is added to the UI
2. Run line Application.Current.Resources.MergedDictionaries.Clear()
3. RichTextBox is added to the UI *Crash*
This does not occur in 2017.1.222, but it does in 2017.2.503 through 2017.2.703
As a workaround until the fix is available, you can merge the required resources before initializing RadRichTextBox after Application.Current.Resources.MergedDictionaries are cleared:
I would like to add that, with the help of Patrick, we managed to reproduce the issues and logged them in our portal. For anyone that might be interested, here are the public items:
- XamlParseException is thrown when the ImageAdornerUI resources are not present in App.Current.Resources or App.Current.Resources.MergedDictionaries
- "Element is already the child of another element" error is thrown design time when more than one RadRichTextbox instances are created