Skip to content

Upgrade from netstandard1.6 to netstandard2.0 #879

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
bergmeister opened this issue Feb 7, 2018 · 1 comment · Fixed by #919
Closed

Upgrade from netstandard1.6 to netstandard2.0 #879

bergmeister opened this issue Feb 7, 2018 · 1 comment · Fixed by #919
Assignees

Comments

@bergmeister
Copy link
Collaborator

As discussed in PR 870 here, @JamesWTruher prefers to move to netstandard2.0 to match it closer to the PowerShell Core repo for consistency that uses netcore2.0, which is practically speaking very similar to netstandard2.0
This has the only disadvantage that netstandard2.0 is not implemented by netcore 1.x runtimes and reduces the number of devices on which it can run under due to the vast increase of the APIs. However, since the usage of PowerShell products currently only applies to devices that have the netcore of full .net runtime (but not mobile runtimes such as Mono), this should not be an issue and reduce its practical usage. Therefore for simplicity and the ability of having more APIs, the plan is to perform the upgrade, which should help development due to the API increase and re-evaluate the netstandard question again until there is actually a use case where a lower netstandard is required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant