[Collapse]General Information
 [Expand]What's Included
 [Collapse]Installation
  [Expand]Download the .NET Products Installer
  [Expand]Install DevExpress .NET Products
  [Collapse]Install DevExpress Controls Using NuGet Packages
    Obtain Your NuGet Feed URL
    Setup Visual Studio's NuGet Package Manager
    Manage Packages Using Dotnet CLI
    Manage Packages Using NuGet CLI
    Updating Packages
    NuGet Limitations and Troubleshooting
    .NET Core controls via NuGet
   Upgrade Notes
  License Agreement
  Help Resources
  Support Services
  Developer Express Inc Trademarks
[Expand]WinForms Controls
[Expand]ASP.NET Controls and MVC Extensions
[Expand]ASP.NET Bootstrap Controls
[Expand]ASP.NET Core Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Office File API
[Expand]Reporting
[Expand]Report and Dashboard Server
[Expand]Dashboard
[Expand]eXpressApp Framework
[Expand]eXpress Persistent Objects
[Expand]CodeRush
[Expand]CodeRush Classic
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation
View this topic on docs.devexpress.com (Learn more)

NuGet Limitations and Troubleshooting

Expanded Limitations

Manually adding DevExpress packages and their dependencies to a project using NuGet imposes the following limitations:

  • No design-time assemblies are provided.
  • Runtime assemblies are provided starting with version 16.2.
  • Assemblies from NuGet packages do not affect the IDE - DevExpress controls installed using NuGet are not available in the Toolbox.
  • The Assembly Deployment Tool does not detect NuGet references.

Expanded Troubleshooting

The section below describes known issues and their workarounds that you may face while using NuGet packages with DevExpress controls.

Using Visual Studio 2010 and Visual Studio 2012 is impossible with NuGet version < 3.4

This issue occurs because DevExpress controls migrated to TLS 1.2 and both VS2010 and VS2012 use a NuGet version that doesn't support this protocol (NuGet version > 3.4).

There are two ways to work around this:

  1. On a system level.

  2. Use NuGet 3.4 and newer.

Is this topic helpful?​​​​​​​