Skip to content

Investigate which TFM's we want to support in 2.0.0 #10

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
akamsteeg opened this issue Aug 18, 2017 · 1 comment
Closed

Investigate which TFM's we want to support in 2.0.0 #10

akamsteeg opened this issue Aug 18, 2017 · 1 comment
Assignees
Milestone

Comments

@akamsteeg
Copy link
Owner

akamsteeg commented Aug 18, 2017

Currently, the library supports three Target Framework Monikers:

  1. NET45
  2. NET46
  3. NETSTANDARD1.5

However, this seems a bit redundant. If we support .NET 4.5, the lowest full framework TFM we can target at the moment, we also implicitly support 4.6, 4.6.1, 4.7, etc. Why do we explicitly specify .NET 4.6 then?

With .NET Standard 1.5 we can run on the full framework in any application targeting .NET 4.6.2 or higher and in .NET Core 1.0 or higher. For consumers being stuck (for the moment?) at older versions of .NET we can give them 4.5.

So, in summary: Wouldn't it be enough to just target NET45 and NETSTANDARD1.5?

@akamsteeg
Copy link
Owner Author

I suggest we leave it at NET45, which we can run on NET46 or higher too, and NETSTANDARD1.5.

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

No branches or pull requests

1 participant