Limitations and Troubleshooting - DevExpress NuGet Packages
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
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.