Flaw Prevents .NET Core 2.1 Updates, Extends Life of .NET Core 2.0
Microsoft announced the end-of-life of last year's .NET Core 2.0 offering has been extended to Oct. 1 because of a flaw that prevents some updates to .NET Core 2.1.
"We intend to fix this issue in the .NET Core August 2018 update," the company said in a blog post. "Based on that timing, we will extend the .NET Core 2.0 EOL date to October 1, 2018. This extension should give those customers affected by this issues a remaining six weeks to move to .NET Core 2.1."
.NET Core 2.0 was released last August, greatly expanding the functionality of the modular, general-purpose, cross-platform, open source development platform maintained by Microsoft, the .NET Foundation and general .NET community.
As a non-Long Term Support (LTS) release, its support life was supposed to end three months after the follow-on release, which was .NET Core 2.1, shipped in late May.
With problems caused by a "narrow but critical diagnostics issue with .NET Core 2.1," support for v2.0 has been extended by a month.
The flaw had some users concerned, with one commenting on the GitHub issue page: "We're on .NET Core 2.0 in prod for many of our services, and we use New Relic. With yesterday's blog post that .NET Core 2.0 will be out of support in ~70 days, we're quite nervous that we will find ourselves in a difficult position soon. Thanks for your work on this issue."
Three days ago, Microsoft provided a follow-up post:
Further follow up for anyone looking for daily 2.2 preview builds. The fix is present in both daily runtime and SDK builds at this point: https://github.com/dotnet/core/blob/master/daily-builds.md.
2.1 servicing is still in progress. Part way through we discovered a 2nd issue (#18602) when using the Visual Studio debugger disassembly window. Although we determined it was pre-existing bug in 2.0 and 2.1, the user visible behavior became worse when combined with the fix for this issue. That 2nd issue now has a fix checked in for daily builds and the 2.1 servicing will include both fixes.
David Ramel is the editor of Visual Studio Magazine.