>No, but I would expect you to read the release announcements. [2]
Yeah, well...where is it?
https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcin...
https://github.com/dotnet/core/blob/master/release-notes/2.0...
Or do you seriously expect me to read every beta/RC release note of versions I won't ever use for elementary issues like this?
In .NET core spies on users by defaultdotnet
core
PowerShell2015–2026
dotnet / core
core
.NET news, announcements, release notes, and more!
80Distinct people
86Mentions
0Explicit recommenders
22.1KGitHub stars
What to know before exploring
What it is
.NET news, announcements, release notes, and more!
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- dotnet/aspnetcore · linked in 2 of the same discussions
- dotnet/roslyn · linked in 2 of the same discussions
- dotnet/vscode-csharp · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:02:50 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year86 dated mentions
Observed mentions: 2015-04-29 21:44:49 UTC to 2026-09-17 14:13:26 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 7 | 3 | 4 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 15 | 3 | 12 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 6 | 1 | 5 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 9 | 1 | 8 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 13 | 1 | 12 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 6 | 4 | 2 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 10 | 4 | 6 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 6 | 1 | 5 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 3 | 0 | 3 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
.NET Release Notes
Welcome to the home of .NET release notes and news.
Releases
Releases under active support or development:
Version
Release Date
Release type
Support phase
Latest Patch Version
End of Support
.NET 11.0
November 10, 2026
STS
Go-Live
11.0.0-rc.3
November 10, 2026
.NET 10.0
November 11, 2025
LTS
Active
10.0.14
November 14, 2028
.NET 9.0
November 12, 2024
STS
Maintenance
9.0.22
November 10, 2026
.NET 8.0
November 14, 2023
LTS
Maintenance
8.0.33
November 10, 2026
Release notes
Binaries and installers
Installation docs
dotnet-install scripts
Discussions
Follow GitHub Discussions, where you will find the latest news on releases, including PSAs and CVEs.
You can subscribe to discussions with the following RSS feeds:
Category
GitHub Discussions
RSS Feed
All Discussions
🔗
🔗
News
🔗
🔗
General
🔗
🔗
Read the full README on GitHubWhat Hacker News says
15 sourcesWe'll see.
I think the netstandard -> all platforms approach, combined with the aggressive depreciation of old .Net 4.6.x versions is a road map for the future.
Maintaining two entire release chains, the 4.x and the .Net core 2.x, is an impossible long term strategy.
I would be absolutely astonished if the 4.x line is quietly folded away and depreciated ('unsupported') once the netstandard surface area means the code bases that no longer run on the .Net core fall to significantly small fraction.
At that point there will just be 'one' .Net again, and it will be .Net core, on all platforms.
Significantly, there seems little to no indication (https://github.com/dotnet/core/issues/43) that winforms and WPF are going to .Net core.
You might argue that Microsoft is a legacy beast, and they won't abandon their developers by dropping support for
Read the rest
old versions, but they already are doing that in the 'you can install it, sure, but it'll never get any more updates' (#1, #2), so you know.
Don't bet the farm on a WPF app. Just saying.
#1: https://blogs.msdn.microsoft.com/dotnet/2015/12/09/support-e...
#2: https://support.microsoft.com/en-us/help/17455/lifecycle-faq...
and yet they also have things like this:
https://github.com/dotnet/core/blob/master/LICENSE.TXT
https://github.com/Microsoft/vscode/blob/master/LICENSE.txt
Can't really say nothing's changed if a lot has. I personally believe they need to refine their OS department, clearly that side of the company needs serious change. I say this after having heard of all the oddities from Windows 10 (their latest and current OS) and how awful it is to remove software from Windows 10.
In Microsoft Becomes Sponsor of Open Source InitiativeHave you considered C#? It only has a single string class. With async-await, concurrency is fine too.
Not long ago, they open sourced the compiler and a subset of runtime, making it cross-platform: https://github.com/dotnet/core It’s a but tricky to install on Linux, but for me it works OK, at least so far (an embedded TCP/UDP server app).
In Some Were Meant for C: The Endurance of an Unmanageable Language [pdf]They talk about this here https://github.com/dotnet/core/blob/master/samples/linker-in...
In Introducing .NET IL Linker> However for .NET, since you can use reflection to load any type in an assembly and call any method dynamically, removing a method is isn't statically called could cause you to fail at runtime.
Indeed. it's not that common, but I would expect it to happen. One example is that many IoC Containers allow you to scan assemblies and register all class + interface pairs that match given rules.
There has to be some safety-hatch to express "yes, I really want to keep that class and its methods. Don't strip them out".
This seems to be documented here: https://github.com/dotnet/core/blob/master/samples/linker-in...
In Introducing .NET IL LinkerThis is neat as it brings smaller DLL sizes. It does not include self-contained executables that can be shipped, however. You still end up having to ship a directory full of DLLs.
I've been wanting self contained executables for a while now. CoreRT (.NET Native) seems to have been put on the backburner, plus sometimes the JIT case is faster.
Source: discussion at https://github.com/dotnet/core/issues/915#issuecomment-32608...
In Introducing .NET IL LinkerThanks for that: https://github.com/dotnet/core/pull/326#issuecomment-2624791... is the clearest instructions for building from source* I've seen.
Note that that still seems to require an existing binary (the bootstrapping problem). I wonder if the Debian CLR people have seen this.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779970
In Performance Improvements in .NET CoreI'm not sure if your "joke" is relevant. .NET core is open source: https://github.com/dotnet/core
In WordPress on .NETFrom the roadmap: "Because of this, if you follow our repositories you will start to see .NET Core 2.0 versioning."[0]
As an aside, I find it helpful to think of .net standard as an interface (API definition, no code), and .net core as a class (implements interface, provides implementation, possibly additional methods).
public class NetCore2_0 : INetStandard2_0 {}
public class NetCore1_0 : INetStandard1_6 {}
[0] - https://github.com/dotnet/core/blob/master/roadmap.md
In The .NET Core 2 WaveI wonder if there is some confusion between .NET Standard and .NET Core. As .NET Standard 2.0 is a thing but I can't find any official reference to .NET Core 2 yet. Obvious, this will eventually come but it's not on the roadmap yet as far as I can see.
https://github.com/aspnet/home/wiki/roadmap
https://blogs.msdn.microsoft.com/dotnet/2016/07/15/net-core-...
Disclaimer: I've not been paying as close attention as I did last year when writing my book on .NET Core (https://unop.uk/book/). So I may just have missed something.
Edit:
I've found some more info: https://github.com/dotnet/core/blob/master/roadmap.md#ship-d...
Milestone Release Date
.NET Core 2.0 Spring 2017
.NET Standard 2.0 Spring 2017
This is weird as I had previously heard this would be v1.2. Perhaps it is but it's now a major bump rather than a minor one. Either a
Read the rest
breaking change or to tie in with .NET Standard?
I guess this means it won't stay aligned with the ASP.NET Core versions now?
I spend time writing a helpful comment and the thread gets flagged. :(