[Collapse]General Information
 [Expand]What's Included
 [Collapse]Installation
  [Expand]Download the .NET Products Installer
  [Expand]Install DevExpress .NET Products
  [Expand]Install DevExpress .NET Core 3 Desktop 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
    Integrate NuGet to Popular Continuous Integration Systems
    NuGet Limitations and Troubleshooting
    Trial .NET Core Controls Via NuGet
    Local NuGet feed
   Upgrade Notes
  Product Versions
  Dual Online Documentation Resources
  Additional Technical Resources
  Support Services
  License Agreement
  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

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

1. Old NuGet.exe version causes "The underlying connection was closed: An unexpected error occurred on send"

2. The "Failed to fetch results from V2 feed at...Response status code does not indicate success: 404 (Not Found)" error when using the loal DevExpress Feed


Old NuGet.exe version causes "The underlying connection was closed: An unexpected error occurred on send"

The DevExpress NuGet feed migrated to TLS 1.2. NuGet.exe supports this protocol starting with v3.4. However, VS2010, VS2012, and VS2013 use an older NuGet version which does not support TLS 1.2.

Solution:


"Failed to fetch results from V2 feed at... Response status code does not indicate success: 404 (Not Found)" message when using the local DevExpress NuGet feed

Visual Studio 2013, Visual Studio 2012 and Visual Studio 2010 create the NuGet V2 feed : https://www.nuget.org/api/v2/. This feed prevents searching packages in a local feed.

Solution:

Remove or disable the https://www.nuget.org/api/v2/ feed or use the NuGet V3 feed instead: https://api.nuget.org/v3/index.json.

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