You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a lot of confusion when searching for packages whose native and managed implementations have the same name.
For example, if I search for "Libjpeg-Turbo", I find the C++ packages containing the native implementations and the .NET packages containing the wrappers.
Additional Context and Details
In certain cases, it is even possible to add a C++ package in a .NET project.
I believe it would be a better developer experience if the VS UI (and probably nuget.org as well) could provide a better visualization of the type of package as well as the possibility to filter out the undesired ones.
The text was updated successfully, but these errors were encountered:
NuGet Product(s) Involved
Visual Studio Package Management UI
The Elevator Pitch
There is a lot of confusion when searching for packages whose native and managed implementations have the same name.
For example, if I search for "Libjpeg-Turbo", I find the
C++
packages containing the native implementations and the.NET
packages containing the wrappers.Additional Context and Details
In certain cases, it is even possible to add a C++ package in a .NET project.
I believe it would be a better developer experience if the VS UI (and probably nuget.org as well) could provide a better visualization of the type of package as well as the possibility to filter out the undesired ones.
The text was updated successfully, but these errors were encountered: