Limitations and Troubleshooting - DevExpress NuGet Packages
- 3 minutes to read
Limitations
When you add DevExpress NuGet packages and their dependencies to a project manually, consider the following limitations:
- We ship NuGet packages with our controls starting with v16.2. In earlier versions, you should create your own NuGet packages with our assembles and organize a local NuGet feed (Create NuGet packages).
- Design-time assemblies are included only for WPF and WinForms Controls. WinForms design-time assemblies are intended to work with .NET Core / .NET 5+ projects. To use these assemblies in .NET Framework projects, you should install DevExpress components on your machine.
- Toolbox support for the WinForms controls has known issues: Design-Time Support for DevExpress WinForms Controls for .NET - FAQ.
- The Assembly Deployment Tool does not detect NuGet references.
Troubleshooting
- Old NuGet.exe version causes “The underlying connection was closed: An unexpected error occurred on send”
- “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
- Errors “403 Forbidden” or “Unable to find package ‘DevExpress.XXX’. Existing packages must be restored before performing an install or update.”
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, Visual Studio 2010, 2012, and 2013 use an older NuGet version that does not support TLS 1.2.
Solution:
- For Windows 7, use the technique described at Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows.
For other OS versions, modify the following registry keys:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\\.NETFramework\v4.0.30319]“SchUseStrongCrypto”=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\\.NETFramework\v4.0.30319]“SchUseStrongCrypto”=dword:00000001
“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 2010, 2012, and 2013 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.
Errors “403 Forbidden” or “Unable to find package ‘DevExpress.XXX’. Existing packages must be restored before performing an install or update.”
If you encounter package installation or update issues in Visual Studio or CI/CD, reset your NuGet package cache with the dotnet tool in Visual Studio itself. In Visual Studio 2017 and higher, use the Tools > NuGet Package Manager > Package Manager Settings menu command, then select Clear All NuGet Cache(s). For more information, refer to the Microsoft documentation.