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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: