An extension for Visual Studio Code that lets you easily add or remove .NET Core 1.1+ package references to/from your project's .csproj file using Code's Command Palette.
MIT License
34
stars
17
forks
source link
Latest NuGet Version not displaying correctly in Visual Studio Code #50
In Visual Studio Code, our Syncfusion NuGet packages are not displaying the correct latest version number. For example, the latest version of the Syncfusion.Blazor (https://www.nuget.org/packages/Syncfusion.Blazor/26.2.9) NuGet package is 26.2.9, but it is incorrectly showing 18.1.0.42 as the latest version in Visual Studio Code.
We discovered that when retrieving the version list using the NuGet Extension in Visual Studio Code (via NuGet API - https://api.nuget.org/v3-flatcontainer/syncfusion.blazor/index.json), the versions are fetched in the wrong order, leading to the incorrect version (18.1.0.42) being marked as the latest. This issue is affecting various Syncfusion NuGet packages, each showing different incorrect versions as the latest. Could you please investigate and resolve this issue as soon as possible?
Hi Team,
In Visual Studio Code, our Syncfusion NuGet packages are not displaying the correct latest version number. For example, the latest version of the Syncfusion.Blazor (https://www.nuget.org/packages/Syncfusion.Blazor/26.2.9) NuGet package is 26.2.9, but it is incorrectly showing 18.1.0.42 as the latest version in Visual Studio Code.
We discovered that when retrieving the version list using the NuGet Extension in Visual Studio Code (via NuGet API - https://api.nuget.org/v3-flatcontainer/syncfusion.blazor/index.json), the versions are fetched in the wrong order, leading to the incorrect version (18.1.0.42) being marked as the latest. This issue is affecting various Syncfusion NuGet packages, each showing different incorrect versions as the latest. Could you please investigate and resolve this issue as soon as possible?