--- title: You Might Not Need to Upgrade: The Case for Staying Put description: A podcast episode argues that upgrading off .NET Framework is not automatically the right call, using Stack Overflow's multi-year, staged migration as a case... canonical: https://daily.dev/posts/you-might-not-need-to-upgrade-the-case-for-staying-put-ocksqzbac twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: You Might Not Need to Upgrade: The Case for Staying Put | daily.dev og:description: A podcast episode argues that upgrading off .NET Framework is not automatically the right call, using Stack Overflow's multi-year, staged migration as a case... og:url: https://daily.dev/posts/you-might-not-need-to-upgrade-the-case-for-staying-put-ocksqzbac og:image: https://api.daily.dev/og/posts/OcKsQZbaC.png og:image:alt: You Might Not Need to Upgrade: The Case for Staying Put og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # You Might Not Need to Upgrade: The Case for Staying Put **[We Are .NET](https://daily.dev/sources/wearedotnet)** · 50 min read · 1 upvotes · 0 comments ## Summary A podcast episode argues that upgrading off .NET Framework is not automatically the right call, using Stack Overflow's multi-year, staged migration as a case study. It walks through actual Microsoft support timelines: .NET Framework 4.8 has no end-of-support date and rides on the underlying Windows OS lifecycle (some editions supported into 2031), while .NET 10 LTS ends November 2028 and .NET 11 (STS) actually expires five days before .NET 10. It highlights a real deadline for ASP.NET Core 2.x on .NET Framework (support ends April 13, 2027) and for .NET Framework 4.6.2 (support ends January 12, 2027, requiring an in-place move to 4.8). The host proposes treating 'stay on the current version' as a documented, reviewable decision rather than an unspoken failure, using Stack Overflow's and Umbraco's histories as evidence that staying put can outlast the systems built to replace them. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### When does support end for ASP.NET Core 2.x running on .NET Framework? Support for ASP.NET Core 2.x (packaged as version 2.3, functionally the same as 2.1) running on .NET Framework ends on April 13, 2027. This affects teams that took the sanctioned half-step of moving their web layer to ASP.NET Core while remaining on .NET Framework. Notably, this deadline does not apply to Web Forms, MVC5, or Web API 2 apps built on System.web, which follow the Windows OS lifecycle instead. _Teams juggling partial ASP.NET Core migrations can track lifecycle deadlines like this one on daily.dev._ ### Does .NET Framework 4.8 have an official end-of-support date? No, .NET Framework 4.8 has no end-of-support date of its own. Starting with version 4.5.2, .NET Framework is treated as a component of the Windows operating system, so it follows the lifecycle of whichever Windows version it's installed on. For example, Windows Server 2022's extended support runs until October 14, 2031, meaning a .NET Framework 4.8 app on that server could be supported years longer than a modern .NET 10 application. _Developers planning runtime upgrades can keep tabs on lifecycle nuances like this via daily.dev._ ### Why does .NET 11 reach end of support before .NET 10 even though it's newer? Because .NET 11 is a Standard Term Support (STS) release, getting 24 months of support from November 10, 2026 to November 9, 2028, while .NET 10 is a Long Term Support (LTS) release ending November 14, 2028. That means .NET 11 expires five days earlier than .NET 10, so upgrading immediately to .NET 11 at launch yields less remaining support than staying on .NET 10. _Teams deciding between LTS and STS .NET releases can weigh trade-offs like this through daily.dev._ ## Similar posts on daily.dev - [End of support looms for .NET 8 and .NET 9](https://daily.dev/posts/end-of-support-looms-for-net-8-and-net-9-dpivhb03i) · InfoWorld · 12 upvotes · 14 comments - [Microsoft calls time on ASP.NET Core 2.3 on .NET Framework](https://daily.dev/posts/microsoft-calls-time-on-asp-net-core-2-3-on-net-framework-2meorjlew) · DEVCLASS · 26 upvotes · 1 comments - [.NET's long-term support is not long-term enough, dev complains](https://daily.dev/posts/net-s-long-term-support-is-not-long-term-enough-dev-complains-zuof1zjtm) · DEVCLASS · 26 upvotes · 5 comments --- Tags: [#.net](https://daily.dev/tags/.net), [#aspnetcore](https://daily.dev/tags/aspnetcore) [View this post on daily.dev](https://daily.dev/posts/you-might-not-need-to-upgrade-the-case-for-staying-put-ocksqzbac) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"You Might Not Need to Upgrade: The Case for Staying Put","url":"https://daily.dev/posts/you-might-not-need-to-upgrade-the-case-for-staying-put-ocksqzbac","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/you-might-not-need-to-upgrade-the-case-for-staying-put-ocksqzbac"},"datePublished":"2026-10-09T08:48:47.486Z","dateModified":"2026-10-09T08:49:10.759Z","description":"A podcast episode argues that upgrading off .NET Framework is not automatically the right call, using Stack Overflow's multi-year, staged migration as a case...","image":"https://i.ytimg.com/vi/v6s9ryu9xZk/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/v6s9ryu9xZk/sddefault.jpg","isAccessibleForFree":true,"articleSection":"We Are .NET","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"We Are .NET","logo":"https://media.daily.dev/image/upload/s--BsnVOa3i--/f_auto/v1718347410/logos/wearedotnet","url":"https://daily.dev/sources/wearedotnet"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/you-might-not-need-to-upgrade-the-case-for-staying-put-ocksqzbac","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":".net,aspnetcore","timeRequired":"PT50M","video":{"@type":"VideoObject","name":"You Might Not Need to Upgrade: The Case for Staying Put","description":"A podcast episode argues that upgrading off .NET Framework is not automatically the right call, using Stack Overflow's multi-year, staged migration as a case...","thumbnailUrl":"https://i.ytimg.com/vi/v6s9ryu9xZk/sddefault.jpg","uploadDate":"2026-10-09T08:48:47.486Z","duration":"PT50M","url":"https://api.daily.dev/r/OcKsQZbaC","embedUrl":"https://www.youtube.com/embed/v6s9ryu9xZk"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"We Are .NET","item":"https://daily.dev/sources/wearedotnet"},{"@type":"ListItem","position":3,"name":"You Might Not Need to Upgrade: The Case for Staying Put"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/you-might-not-need-to-upgrade-the-case-for-staying-put-ocksqzbac#faq","mainEntity":[{"@type":"Question","name":"When does support end for ASP.NET Core 2.x running on .NET Framework?","acceptedAnswer":{"@type":"Answer","text":"Support for ASP.NET Core 2.x (packaged as version 2.3, functionally the same as 2.1) running on .NET Framework ends on April 13, 2027. This affects teams that took the sanctioned half-step of moving their web layer to ASP.NET Core while remaining on .NET Framework. Notably, this deadline does not apply to Web Forms, MVC5, or Web API 2 apps built on System.web, which follow the Windows OS lifecycle instead. Teams juggling partial ASP.NET Core migrations can track lifecycle deadlines like this one on daily.dev."}},{"@type":"Question","name":"Does .NET Framework 4.8 have an official end-of-support date?","acceptedAnswer":{"@type":"Answer","text":"No, .NET Framework 4.8 has no end-of-support date of its own. Starting with version 4.5.2, .NET Framework is treated as a component of the Windows operating system, so it follows the lifecycle of whichever Windows version it's installed on. For example, Windows Server 2022's extended support runs until October 14, 2031, meaning a .NET Framework 4.8 app on that server could be supported years longer than a modern .NET 10 application. Developers planning runtime upgrades can keep tabs on lifecycle nuances like this via daily.dev."}},{"@type":"Question","name":"Why does .NET 11 reach end of support before .NET 10 even though it's newer?","acceptedAnswer":{"@type":"Answer","text":"Because .NET 11 is a Standard Term Support (STS) release, getting 24 months of support from November 10, 2026 to November 9, 2028, while .NET 10 is a Long Term Support (LTS) release ending November 14, 2028. That means .NET 11 expires five days earlier than .NET 10, so upgrading immediately to .NET 11 at launch yields less remaining support than staying on .NET 10. Teams deciding between LTS and STS .NET releases can weigh trade-offs like this through daily.dev."}}]} ```