1 Answer, 1 is accepted
0
Accepted
Hello Markus,
This is a common issue when using XAML included binaries (from Binaries folder of the installation directory) and setting a theme implicitly - by merging theme resource dictionaries in App.xaml. This could be resolved by making sure all the assemblies are noXaml (from Binaries.noXaml folder) or by choosing to use StyleManager as theming mechanism and setting StyleManager.ApplicationTheme = new FluentTheme(); in code behind before the InitializeComponent(); of the MainWindow and removing the theme resource dictionaries from the App.xaml if they are not needed.
The best way to make sure if all the binaries are noXaml is to comment out the resources in App.xaml, rebuild and then the controls should not be visible runtime. The noXaml mechanism provides much smaller assemblies since the control assemblies do not have all the markup for all them themes included and rely on external styles from a theme assembly.
I hope this would be helpful in dealing with the issue. I you have any other questions, please do not hesitate to contact us further.
Regards,
Martin
Progress Telerik
This is a common issue when using XAML included binaries (from Binaries folder of the installation directory) and setting a theme implicitly - by merging theme resource dictionaries in App.xaml. This could be resolved by making sure all the assemblies are noXaml (from Binaries.noXaml folder) or by choosing to use StyleManager as theming mechanism and setting StyleManager.ApplicationTheme = new FluentTheme(); in code behind before the InitializeComponent(); of the MainWindow and removing the theme resource dictionaries from the App.xaml if they are not needed.
The best way to make sure if all the binaries are noXaml is to comment out the resources in App.xaml, rebuild and then the controls should not be visible runtime. The noXaml mechanism provides much smaller assemblies since the control assemblies do not have all the markup for all them themes included and rely on external styles from a theme assembly.
I hope this would be helpful in dealing with the issue. I you have any other questions, please do not hesitate to contact us further.
Regards,
Martin
Progress Telerik
Want to extend the target reach of your WPF applications, leveraging iOS, Android, and UWP? Try UI for Xamarin, a suite of polished and feature-rich components for the Xamarin framework, which allow you to write beautiful native mobile apps using a single shared C# codebase.