Skip to content

Bump minimum target framework version to 4.5.1 #379

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

Merged
merged 3 commits into from
Feb 10, 2018

Conversation

fsateler
Copy link
Member

@fsateler fsateler commented Feb 6, 2018

As per the .Net framework lifecycle policy as of today, all versions below 4.6
are unsupported (except 3.5 but we don't support that anyway).

https://support.microsoft.com/eu-es/help/17455/lifecycle-faq-net-framework

As per the .Net framework lifecycle policy as of today, all versions below 4.6
are unsupported (except 3.5 but we don't support that anyway).

https://support.microsoft.com/eu-es/help/17455/lifecycle-faq-net-framework
It is supported on all target versions
@atifaziz
Copy link
Member

atifaziz commented Feb 7, 2018

all versions below 4.6 are unsupported

Where do you see that? Per the policy, 4.5.2 is bound with the lifecycle policy of the parent operating system:

.NET Framework 4.5.2: Support for .NET 4.5.2 follows the lifecycle policy of the parent operating system. It is supported as a Windows component on the latest required operating system update for Windows Vista SP2, Windows 7 SP1, Windows Server 2008 SP2, Windows Server 2008 R2 SP1, Windows 8.1 Update, Windows Server 2012, and Windows Server 2012 R2.

Considering the product lifecycle of Windows 2012 R2 Standard, .NET 4.5.2 would be supported at least as far out as 2023, though mainstream support ends October of this year:

Products Released Lifecycle Start Date Mainstream Support End Date Extended Support End Date
Windows Server 2012 R2 Standard 25/11/2013 09/10/2018 10/10/2023
Windows Storage Server 2012 R2 Standard 25/11/2013 09/10/2018 10/10/2023

Anyway, we don't work for Microsoft so we're not bound by those dates, just the threshold for pain to support a particular target. We can certainly drop 4.5.1:

.NET Framework 4.5.1: Support for .NET Framework 4.5.1 on all operating systems ended on January 12, 2016.

Any reason to skip 4.5.2 and bump to 4.6 here?

@fsateler
Copy link
Member Author

fsateler commented Feb 7, 2018

all versions below 4.6 are unsupported

Where do you see that? Per the policy, 4.5.2 is bound with the lifecycle policy of the parent operating system

Oh dear. Embarrassing. It appears I need glasses 👓 .

Any reason to skip 4.5.2 and bump to 4.6 here?

No, not at all. I'll rework to use 4.5.2

Anyway, we don't work for Microsoft so we're not bound by those dates, just the threshold for pain to support a particular target.

We are not bound, I agree. Yet we don't need to take on the pain of supporting old stuff for too long. I find that the upstream support timeframes are a good Schelling point for providing upper limits for target support.

@atifaziz atifaziz changed the title Bump minimum target framework version to 4.6 Bump minimum target framework version to 4.5.1 Feb 10, 2018
@atifaziz atifaziz merged commit c0d23a8 into morelinq:master Feb 10, 2018
@atifaziz atifaziz added this to the 3.0.0 milestone Feb 10, 2018
@atifaziz atifaziz changed the title Bump minimum target framework version to 4.5.1 Bump minimum target framework version to 4.5.2 Feb 10, 2018
@atifaziz atifaziz changed the title Bump minimum target framework version to 4.5.2 Bump minimum target framework version to 4.5.1 Feb 10, 2018
@atifaziz atifaziz modified the milestones: 3.0.0, 3.0.0 βeta 1 Apr 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants