Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

netstandard2.0 version depends on unsupported ASP.NET Core version 2.2 #993

Closed
vidrenning opened this issue Jan 26, 2024 · 0 comments · Fixed by #994
Closed

netstandard2.0 version depends on unsupported ASP.NET Core version 2.2 #993

vidrenning opened this issue Jan 26, 2024 · 0 comments · Fixed by #994

Comments

@vidrenning
Copy link
Contributor

Hello, I am trying to use SoapCore in an ASP.NET Core 2.1 project that runs under .NET Framework 4.7.2. ASP.NET Core 2.1 is still supported by Microsoft, specifically for scenarios where ASP.NET Core must be run under .NET Framework. Source: https://dotnet.microsoft.com/en-us/platform/support/policy/aspnet

However the issue is that SoapCore depends on Microsoft.AspNetCore.Http 2.2.0. This version is not supported anymore by Microsoft. When looking at https://www.nuget.org/packages/Microsoft.AspNetCore.Http, you can see that the newest version 2.2.2 from the 2.2 branch is from 2019, but the newest version 2.1.34 from the 2.1 branch is from 2022. The version 2.2.2 is marked as deprecated, but version 2.1.34 is not.

In this link you can see the list of supported ASP.NET Core 2.1 packages: https://dotnet.microsoft.com/en-us/platform/support/policy/aspnet/2.1-packages

Is it possible for SoapCore to depend on the supported ASP.NET Core 2.1 packages instead of the deprecated 2.2 packages? The 2.1 packages most likely contain fixes for security issues, so it would be better to use these packages.

vidrenning added a commit to vidrenning/SoapCore that referenced this issue Jan 31, 2024
Lowered referenced package versions because the 2.1 versions are
supported by Microsoft, while the 2.2 versions are not.

Fixes DigDes#993
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant