NuGet Limitations and Troubleshooting
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.
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.
- For Windows 7, use the approach 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 manually:
[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