The reason why you were advised to reference the normal assemblies in your ticket was the fact that we thought that you were using the StyleManager
to apply a theme in your application.
However, please note that the StyleManager
although very convenient, was our solution to the lack of implicit styles available within the previous versions of WPF. Once you set a theme through the StyleManager
, it basically applies a style on the appropriate control(s). However, now that WPF supports implicit styles you can easily create even application-wide themes.
On top of that, with the implicit styles approach, you have all xaml resources available in your application and you can track any style-related dependencies or change the style settings to customize the default appearance of a component. Moreover, you can use our NoXaml assemblies and add only the styles that you actually need in your application. This way you will minimize the size of your application.
This is why I'd recommend the more native approach - using implicit styles and taking advantage of our NoXaml assemblies in your application. In that case you can follow the guidence provided above to apply a theme on the RadRibbonWindow
Please let us know if you need more information.
TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>