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

Consider switching to netstandard2.1 #2882

Open
ewoutkramer opened this issue Oct 3, 2024 · 2 comments
Open

Consider switching to netstandard2.1 #2882

ewoutkramer opened this issue Oct 3, 2024 · 2 comments
Labels
breaking change This issue/commit causes a breaking change, and requires a major version upgrade

Comments

@ewoutkramer
Copy link
Member

Although we currently do not use newer features, supporting netstandard 2.0 is becoming a burden. In particular, to give us more freedom to change APIs in the SDK6 timeframe, I would like to at least move to netstandard2.1 to be able to use default interface implementations. It would also allow us to simplify string operations by using slices.

We have also thought about jumping onto the .NET Core bandwagon, so actually releasing for a .NET version (say, 6.0 or 7.0). This of course will cause our code no longer to run on Unity or Xamarin, but .NET is widely supported on Mac, Android, Linux and Windows, so I am not sure this is a problem.

@ewoutkramer ewoutkramer added breaking change This issue/commit causes a breaking change, and requires a major version upgrade enhancement labels Oct 3, 2024
@mmsmits
Copy link
Member

mmsmits commented Oct 3, 2024

Maybe we should ask the dotnet stream on Zulip as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change This issue/commit causes a breaking change, and requires a major version upgrade
Projects
None yet
Development

No branches or pull requests

2 participants