Edit this page

Automatic Dependency Resolving

To improve the experience of your clients and reduce your application’s size it is crucial to use only the subset of Telerik UI for WPF assemblies you really need, as described in the Installation and Deployment Section.

Some controls require multiple assemblies and mistakes are likely to happen. For example, in the urge to optimize, you could remove an assembly the project needs, thus breaking the application compilation.

When using the New Project Wizard or Project Configuration Wizard, the possibility to make such mistakes is lowered to a minimum, thanks to the dependency analysis in the Visual Studio Extensions.

Project Configuration Wizard

The VSExtensions assembly list control is controlled by the dependency analyzer, which will not let you select Telerik UI for WPF assemblies without selecting the assemblies they depend on. Both the aspects are covered:

  • Selecting a Telerik UI assembly will also select the additional assemblies it depends on as well.

  • Deselecting a Telerik UI assembly will also deselect assemblies depending on it along with it.

Note that not all assemblies are listed.

See Also

Was this article helpful? Yes No

Give article feedback

Tell us how we can improve this article

Dummy