RichTextBox: Loading ImageAdorner's resources causes XamlParseException in the designer
When RichTextBox is added to the project, the following exception is thrown in the designer:
XamlParseException: Cannot find a Resource with the Name/Key thumbResizeMargin [Line: 26 Position: 49].
Fix available in LIB Version 2017.2.619.
Posted on:06 Jul 2017 16:07
After further discussion, we managed to reproduce the reported errors and logged two additional items:
Posted on:05 Jul 2017 19:01
FYI This occurs in runtime if:
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
Posted on:27 Jun 2017 14:17
New issue in the designer with both 2017.2.619 and today's build of 2017.2.627. "Element is already the child of another element."[see pic] I'm not sure if this would translate to production the way the previous issue has. As I said it's very difficult to observe during runtime, but occurs consistently in the designer. BTW this is VS2015, VS2017 isn't compatible with SL.
Our theme is set using Application theme, and separately with telerik:StyleManager.Theme="Expression_Dark". We only reference the full new DLLS and ignore everything in "Themes.Implicit"
We aren't using theme resources as is
<ResourceDictionary Source="/Metro;component/Themes/Metro/ComboBox.xaml" />
As a follow up to my previous comment, this issue is probably caused by the fact the you are using older themes resources. We have done major refactoring related to introducing the new Material theme in UI for WPF, and the code is partially shared. This is why I would ask you to merge the official XAML resources in order to avoid incompatibilities.
Posted on:27 Jun 2017 06:14
Did you try using LIB Version 2017.2.619? If not, please give it a try and in case the issue is still present with it, I would like to ask you to open a support ticket and attach a sample runnable project reproducing the issue.
Posted on:26 Jun 2017 17:59
We are getting this in production as well on 2017.2.614. It's causing the "White screen of death" which is failing our entire application. This is on SL and the problem is intermittent, perhaps 1/30 times does it happen. Please push a release build fix ASAP.
Posted on:20 Jun 2017 06:00
The fix is included in our Latest Internal Build(LIB) with version 2017.2.619. It should be available under your account. Could you verify whether the issue still exists with this LIB version? If that so, I would ask you to open a support ticket and provide a sample project reproducing the issue.
Posted on:17 Jun 2017 22:37
Note: This is happening in production, not just at design time.
Posted on:17 Jun 2017 22:37
I just upgraded to the latest version and am having this problem as well. I don't see an internal build yet after 2017 R2 SP1. This is blocking my use of RichTextBox in my entire application, so please publish a fix as soon as possible.
Posted on:09 Jun 2017 12:00
The issue is reproduced in SL with StyleManager (XAML-included binaries) only in design time. We have a fix candidate and it should be available in the latest internal build the week after 2017 R2 SP1.
Posted on:08 Jun 2017 15:58
We are currently researching the issue and will post our findings when we are ready here and in the support thread as well.
Posted on:06 Jun 2017 17:10
Also, is this a problem with the *trial* version only? Or will this occur even if we purchased the package?
Posted on:06 Jun 2017 16:08
Is there a workaround? I reported this error when running the Telerik installation wizard, but that is surely just one of a hundred ways of getting the RichTextBox into a Silverlight UserControl. There must be some other way I can put it in a UserControl and have it work properly, right?