10 Answers, 1 is accepted
Just to add on that i am using StyleManager method to apply the theme
Then when you select it, it will enter the selected state of PropertyGridField, the selected foreground will turn to black. [/quote]
Apparently that's not happening and i would like to know how to make it work.
Thank you for the detailed report.
After investigating the cause for it, it seems that this is an issue on our end. I have passed it to our front-end team and the fix will be available with one of the next internal builds. It seems, however, that the problem is reproduced only with StyleManager. Can you please clarify whether using NoXAML binaries with implicit styles is an option for you? More information on this manner can be found in the Implicit Styles topic.
Unfortunately, using NoXAML binaries is not an option i can take at this moment.
(Note: i have tried it but too many codes are impacted).
Please keep me posted once the internal build is ready for download.
Thank you for this clarification.
The fix for the issue will be available with our next internal build on Monday(or Tuesday), so you can give it a try next week.
The bug is fixed. Thanks.
p/s: for anyone encounter this alarm:
For some unknown reason, after making reference to the latest internal build - version 2018.2.820.40, all telerik controls are showing the error - The name "RadXXX" does not exist in the namespace "http://schemas.telerik.com/2008/xaml/presentation".
I am using VS2017 & the target .net framework is 4.0
Can you let me know how to resolve this problem?
Thanks for the image provided.
This is a common issue when upgrading the assemblies versions. Most commonly it is related to the caching mechanism of Visual Studio. In order to overcome this you can do the following steps.
1. Remove all Telerik references from the project.
2. Close VisualStudio.
3. Delete the "bin" and "obj" folders of the project.
4. Reopen VisualStudio and reference the Telerik assemblies. You need to ensure that all assemblies are of the same version and that there is no mixture between XAML and NoXAML binaries. Also, the .NET version of the dlls has to be compatible with the target framework of the project.
5. Clean and then Rebuild the project.
I hope this helps, Joel. Let me know how it goes.
Thanks for the hint.
At the end, i think cleaning the Shadowcache folder solve the problem.
Thank you for the update.
I am happy to hear that you have managed to solve the problem.
All the best,