[Collapse]General Information
 [Expand]What's Included
  [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]Report and Dashboard Server
[Expand]eXpressApp Framework
[Expand]eXpress Persistent Objects
[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

When you add DevExpress NuGet packages and their dependencies to a project manually, consider 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, therefore the Toolbox does not display DevExpress controls installed using NuGet.
  • The Assembly Deployment Tool does not detect NuGet references.

Expanded Troubleshooting

Visual Studio 2010, Visual Studio 2012, and Visual Studio 2013 cannot be used with NuGet version < 3.4.

The DevExpress NuGet feed has recently migrated to TLS 1.2. However, VS2010, VS2012, and VS2013 use a NuGet version (> 3.4), which doesn't support TLS 1.2. To work around this, follow the steps below.

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