-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add additional TFM #88
Comments
Totally makes sense. |
Okay, I checked it and since it targets .NET Standard 2 it covers all the possible targets including .NET Framework 4.6.1. Therefore, you shall have no issue referencing the package, but perhaps you meant the number of packages pulled from Nuget even if most of them only forwarding types to .NET Framework dlls, right? |
Correct I am wanting to reduce the number of dependencies being brought in from nuget.org as it is additional packages needing to be maintained. |
@eiriktsarpalis, is the idea of using .NET Framework 4.6.2 as a target for |
No, I think it's just because net462 is still supported but it also doesn't implement netstandard2.0 (IIRC net47x is the earliest TFM that implements it) |
Actually .NET 4.6.2 implements .NET Standard 2.0 according to the docs and what I see for the package. So, What would be your advice on the topic? I mean the position according to the guidelines for .NET ecosystem. |
Is your feature request related to a problem? Please describe.
I want to minimise dependencies in my project by utilising framework dependencies wherever possible
Describe the solution you'd like
I want the package to not have an explicit dependency on System.Text.Json as it can be provided by the framework when also targeting net 6.
Describe alternatives you've considered
Accept the additional dependency
Additional context
n/a
The text was updated successfully, but these errors were encountered: