Skip to content

Remove netcoreapp3.1 and net5.0 from TargetFrameworks and add net8.0 #8050

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

Closed
gpetrou opened this issue Mar 5, 2024 · 1 comment · Fixed by #8052
Closed

Remove netcoreapp3.1 and net5.0 from TargetFrameworks and add net8.0 #8050

gpetrou opened this issue Mar 5, 2024 · 1 comment · Fixed by #8052
Labels
8.x Relates to a 8.x client version Area: Build Category: Enhancement

Comments

@gpetrou
Copy link
Contributor

gpetrou commented Mar 5, 2024

Is your feature request related to a problem? Please describe.
Currently, I see in the csproj files <TargetFrameworks>netstandard2.0;net461;netstandard2.1;netcoreapp3.1;net5.0;net6.0</TargetFrameworks>

Describe the solution you'd like
Remove netcoreapp3.1 and net5.0 and add net8.0.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

@gpetrou gpetrou added the Feature label Mar 5, 2024
@flobernd flobernd added the 8.x Relates to a 8.x client version label Mar 5, 2024
@flobernd
Copy link
Member

flobernd commented Mar 5, 2024

Thanks for hinting this. Removing the "end of support" targets is probably a good idea. net461 should be replaced by net462 as well. I have to check if we introduce any breaking change that way, but in theory netstandard2.0 and netstandard2.1 should still ensure compatibility with netcoreapp3.1 and net5 projects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.x Relates to a 8.x client version Area: Build Category: Enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants