Skip to content
This repository has been archived by the owner on Mar 7, 2019. It is now read-only.

Migration to dotnet standard #29

Open
baywet opened this issue Oct 10, 2017 · 2 comments
Open

Migration to dotnet standard #29

baywet opened this issue Oct 10, 2017 · 2 comments

Comments

@baywet
Copy link
Collaborator

baywet commented Oct 10, 2017

Since .net standard is the way forward for libraries, it'd be a good thing to migrate the project.
Advantages would be:

  • Support of non Microsoft platforms
  • General performances improvements
  • Standardized set of API's available

https://docs.microsoft.com/en-us/dotnet/standard/net-standard#comparison-to-portable-class-libraries

@kenakamu
Copy link
Owner

I totally agree on this. Which .net standard version you are thinking about?

@baywet
Copy link
Collaborator Author

baywet commented Oct 16, 2017

At this moment I am not sure, my understanding is the lowest version you target the more platforms might be compatible but the less apis you will have access to add part of the standard (and less libraries you might find). There's also the question of the available projects templates that evolved over time as well as the tooling associated to those.
So I think the goal is to find a sweet spot to avoid having too much trouble and/or rewriting too much code.
I believe version 1.1 added quite a few apis top the barbone v1 and brought a lot of improvements. So I guess I'd aim for that and see what happens if I had to do it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants