HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
dotnet
core
PowerShell2015–2026
dotnet / core

core

.NET news, announcements, release notes, and more!

Productivity
Explore on GitHubRead Hacker News discussions
80Distinct people
86Mentions
0Explicit recommenders
22.1KGitHub stars
REPOSITORY AT A GLANCE

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

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, 6:01:08 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.

0510152015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 7 mentions; 3 submissions, 4 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 15 mentions; 3 submissions, 12 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 13 mentions; 1 submissions, 12 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 6 mentions; 4 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 10 mentions; 4 submissions, 6 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments. Incomplete calendar period.2026*

* 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
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC303
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC734
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC15312
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC615
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC404
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC918
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC13112
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC642
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC413
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC1046
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC615
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC303

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 GitHub

What Hacker News says

7 sources
oblio·Sep 6, 2016
.NET Core is slowly reimplementing/integrating all truly cross platform .NET classic APIs (https://github.com/dotnet/core/blob/master/roadmap.md). My guess is that at this point they didn't have the bandwidth to include what you're talking about in the first version but they will include it later on. Long term Mono is probably just going to become a sort of .NET "distribution" on top of .NET Core, it will include things which Microsoft deprecated such as Winform. And it will probably be not maintained at the same level .NET Core itself is. I don't think there will be any reason to use Mono in the future, except for legacy Mono apps...
In Lessons Learned while Converting from ASP.NET to .NET Core
mintplant·Jul 25, 2016Submission

Ask HN: Can anyone from Microsoft clarify the Windows API Code Pack license?

This is a bit of a long shot, but I know some of the .NET developers are here on HN and I don't have a better line into MS. The Windows API Code Pack [0] is a collection of C# utilities for applications built on Windows: shell utilities, wrappers around file open/save dialogs, etc. It looks like development stopped back in 2014, but it's still really useful and gets ~42 downloads/day according to NuGet [1]. Unfortunately the original license page linked from the directory (a code.msdn.microsoft.com address) no longer resolves [2]. User aybe on GitHub, who now maintains the NuGet packages, rescued a copy from the Internet Archive, which reveals a custom, Microsoft-specific license [3]. My question: now that .NET is embracing OSS, would it be possible to update this project's license to something more standard? .NET Core [4] is dual-license
Read the rest
d under MIT and Apache2, for example. [0] https://github.com/aybe/Windows-API-Code-Pack-1.1 [1] https://www.nuget.org/packages/WindowsAPICodePack-Shell/ [2] http://code.msdn.microsoft.com/WindowsAPICodePack/Project/License.aspx [3] https://github.com/aybe/Windows-API-Code-Pack-1.1/blob/master/LICENCE [4] https://github.com/dotnet/core
16 points · Open discussion
judah·Jun 27, 2016
It's the first version of .NET that's cross-platform, it's the first version of .NET that's totally open source, and it's the first version of .NET that can build self-contained apps (no need to have .NET Framework installed to run .NET Core 1.0 apps). See the release notes[0] for more info. It's called "core", because it doesn't contain the Windows desktop UI toolkits, like Windows Forms and Windows Presentation Foundation (WPF), and excludes some other Windows-specific functionality. Additionally, this is the first version of .NET in which apps can be totally self-contained. Previously, you'd need to install the .NET Framework on your machine to run .NET apps. That is no longer a requirement in .NET Core 1.0. So, it's a pretty huge release. And really the first time in decades that MS has built it's premier dev stack with multiple OS su
Read the rest
pport. [0]: https://github.com/dotnet/core/blob/master/release-notes/1.0...
In Announcing .NET Core 1.0

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.