Last Updated: 14 Jan 2022 08:57 by ADMIN
Created on: 29 May 2020 13:09
Category: UI for WPF
Type: Bug Report
Themes: Missing references in Themes projects
We distribute two types of themes solutions with our source code. The first one are: Themes.Sources.sln (for Silverlight), Themes.Sources_WPF.sln and Themes.Sources_NetCore.sln which are used to rebuild our themes. The second one are those without Source in their names, which are used to distribute the output files. Adding references there will remove the errors which appear.
1 comment
Posted on: 14 Jan 2022 08:57


The status of this feature request is now changed to Declined.

The reason behind this decision is that the Themes and Themes.Implicit solutions and their containing projects were once added as a more convenient way of gathering all .xaml resource files (ResourceDictionaries) for all Telerik themes at one place. This is now possible for example with the Visual Studio IDE and its "Open a local folder" option.

After several discussions, we came to the conclusion that the Themes and Themes.Implicit slns and their projects will no longer be a part of the Telerik UI for WPF Distribution. There have been several support threads from which it seems that the clients are left with the incorrect impression that editing any part of the containing output XAML file and then building either the sln or any of its projects will produce ready-to-use custom theme dlls.

From the R1 2022 Release of the Telerik UI for WPF on, the themes folders that come with each Telerik UI for WPF installation will only contain the output XAML files built against your preferred theming mechanism (StyleManager/NoXaml).

Best Regards,
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.