-
-
Notifications
You must be signed in to change notification settings - Fork 372
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
Target framework 4.5.2 in 2.x versions #79
Comments
Yes, I take the opportunity when converting to .net standard to also upgrade .net framework version. Also note that for now v2 has only some bug fixes, there aren't new features, so you can also evaluate to continue to use v1. |
Well, drop 4.5 is a big deal in my opinion. Drop 4.0, which v1.x supported,
it's ok, but there are a lot of 4.5 out there.
I cannot upgrade because i've just upgraded from 4.0 to 4.5.
And if you think about, which features from the new framework you plan to
use? If none, I think supporting at least 4.5.2 it's better. Well, that's
just my opinion thou
…On qua, 2 de mai de 2018 at 10:17 Davide Icardi ***@***.***> wrote:
Yes, I take the opportunity when converting to .net standard to also
upgrade .net framework version.
I can probably also support .net 4.5, but I should check. For you is not
possible to upgrade? Because nowdays there are a lot of packages that start
to drop support for older frameworks.
Also note that for now v2 has only some bug fixes, there aren't new
features, so you can also evaluate to continue to use v1.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#79 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKFqnX_CrnpR51VbGdrZGaqmKIsGDpmks5tubHugaJpZM4TuqWE>
.
|
Ok, I will try to add .net 4.5 support for the next release. |
@davideicardi |
@moh-hassan If you are able to create a pull request I will be happy to merge it. Thanks |
PR is Done :). |
Fixed with #102 |
Why the sudden drop support for framework 4.5.2? I cannot install the new nuget in the a project targeting 4.5.2.
Was this intended?
The text was updated successfully, but these errors were encountered: