>> Please note that this forum targets the RadMap for WPF product. If you
have questions for different product or a common questions I would ask
you to open a new thread in the corresponding forum section. <<
No worries; I just found this thread via Google and it looked like it was on topic, so I replied to it.
>> But, if there are other resource in the Resources dictionary where you add the resource with the merged the themes, you will
probably need an x:Key or just wrap the other resources in a new
dictionary in the merged resources.<<
I figured this one out; I had a System::String outside <ResourceDictionary> and from what I read, it implicitly gets layered into a new ResourceDictionary by the compiler. So adding this string inside the <ResourceDictionary> for the Telerik theme lines, fixed that problem. The System::String is something that Telerik requires us to have in the App.xaml file for assembly protection purposes, else I would not even have run into this conflict.
>> In order to apply an implicit theme you will need to include the NoXaml
version of the UI for WPF dlls along with the theme dll (example:
Telerik.Windows.Themes.Windows8). Then you will need to merge the themes
resources. For example, you can do this in the App.xaml so that the
theme is applied to all controls in the application. You can read the Setting a Theme (Using Implicit Styles) help article to see how this is done. <<
Doing all of that. Switched from regular dlls to NoXaml ones. Added a reference to Telerik.Windows.Themes.Windows8.dll. Added the App.xaml stuff. Read that article multiple times now and ended up searching and finding this thread.
>> I guess the question is which project to build in order to get implicit
themes dlls. If so, the project you need is Themes.Implicit_WPF.sln. <<
Ok, this is what I assumed, so that's what I had tried (amongst other things).
>> As for your last reply, I am not sure why you are using the .bat files from the source code folder <<
Well, initially I was building every solution manually, and when that didn't work, I resorted to giving the batch files a shot out of pure desperation. They appear to work (everything builds), but when I follow the prescribed steps to reference the NoXaml dlls (the ones I built) and the Theme dll (the one I built), and include the merged resources, it doesn't work. I get the BSOD (where B = black).
>> Are you building the source code or the demos of the ribboview? <<
>> Do you have any changes in the source code? <<
Yes, for a variety of reasons including:
1. So the Telerik source would compile (potentially an issue with different version of C# compiler in one location).
2. To meet Telerik licensing requirements (we are explicitly told to modify source to meet those requirements).
3. To fix or work around issues with the RibbonView.
4. Removing project references to files that don't exist (class diagrams). In one location.
But since I know you will ask this question, yes, I have tried reverting all custom changes to the code, rebuilding everything, and this still did not help.
>> Note that the StyleManager is our old theming mechanism. We recommend our new implicit styles theming which brings few additional benefits and resolves some of the StyleManager's limitation. Also, we put our front-end efforts in the implicit styles and all our new themes (currently Office2013, VisualStudio2013, Green) support only
the implicit styles mechanism.<<
Precisely why I am trying to switch from StyleManager, although my issue is more with the Windows8 theme (less colors/granularity) than the StyleManager itself. I want to try the VisualStudio2013 theme and realize that I need to use the Implict theme support to do this.
>> So, in a long term perspective the implicit styles is definitely the better choice.<<
Again, precisely why I am subjecting myself to this discomfort. :)
I think I might grab the Telerik compiled assemblies, and start with a clean project just to make sure that I can get things to work with that, then, if that gives me any insights on to why it's not working with the actual project (when StyleManager seems to work just fine), I will post an additional question in the correct forum and/or contact support directly.