Moving from installed version to nuget version results in blank controls

[Sebastian]

Hello,

I just changed all project references from referencing the installed dll's (Progress\Telerik UI for WPF R1 2023\Binaries\WPF45) to nuget version (e.g. Telerik.Windows.Controls.GridView.for.Wpf.Xaml). Unfortunately, this results in some controls not redering at all any more.

I see this especially at <telerik:Label>, <telerik:Button> and <telerik:GroupBox> (using xmlns:telerik="http://schemas.telerik.com/2008/xaml/presentation")

If I instead use the standard WPF <Label> in the exact same XAML file, the label gets rendered.

Is there anything special one has to apply/change/update if changing from the "installed" version of Telerik for WPF to the nuget based version?

 

Any help or idea much appreciated,

Sebastian

[Martin Ivanov]

Hello Sebastian,

This issue usually refers to the usage of the Telerik NoXaml dlls. You can read more about this in the Missing Controls in the UI article.

Additional to the information in the article, I would suggest you to make sure that all installed Telerik nuget packages point to a version that has .Xaml in its name. For example:

• Telerik.Windows.Controls.for.Wpf.Xaml
• Telerik.Windows.Controls.GridView.for.Wpf.Xaml
• Telerik.Windows.Controls.Navigation.for.Wpf.Xaml
• etc.

I hope that helps.

Regards,
Martin Ivanov
Progress Telerik

[Sebastian]

I thought I already did, but after your reply I checkd all again and really found one that did not point to the .xaml version. After changing that, all now works.

Side question: Why is this .xaml at the end of the nuget name? If it is not allowed to mix, why not naming them like "Telerik.Windows.Wpf.Xaml.Controls" for the xaml version and "Telerik.Windows.Wpf.NoXaml.Controls" for the NoXaml version? This would order much better, and also allows for proper filtering... (Just thinking out loud here)

[Martin Ivanov]

I am glad to hear that the suggestion helped. As for why there is no NoXaml in the end of the nuget package names, the naming follows the assembly name which is why the Wpf and Xaml words aare not in the middle of the package name. Also, you will notice that there is no NoXaml in the names at all. That is a legacy decision from back in time when NoXaml was meant to be the main theming approach. The package without any extra words (kind of the default package) would contain the NoXaml dlls. During the years, the Xaml based approach regain popularity so this is no longer relevant. I am guessing that changing the naming at this point will cause a considerable amount of breaking changes.