Pillar guide

.NET Core: a working guide for .NET developers

Updated May 06, 2026

This guide is the entry point for .NET Core on dotnetnews.co. It collects the writing we have curated on .NET Core into one page so you can orient yourself fast: what .NET Core is in working .NET projects today, why it matters, what to read next, and where teams keep tripping over the same problems.

If you want the full back-catalog, the .NET Core topic page lists every issue we have ever tagged with dotnet-core (currently 256 curated issues). This pillar narrows that down to the pieces that earn re-reading and threads them into a working narrative.

What .NET Core actually is in a working .NET project

In .NET teams we see in 2025 and 2026, .NET Core is rarely a single feature pulled off a shelf. It is a set of practices that touches your build, your test loop, and the way you describe your system to the next person who joins. It is also moving target: the .NET 8 -> .NET 10 cycle changed defaults, the C# language has shipped new sugar nearly every year, and the tooling around .NET Core has consolidated faster than most teams can keep up with.

That makes a curated reading map valuable. Most working developers do not have the cycles to read every release-notes post, every Azure devblog, and every Medium write-up. The .NET News Daily archive does that triage. This page lifts the most useful threads out of that archive and points to where to start.

If you are new to .NET Core or coming back after a long break, read the first three issues in the reading map below in order. They give you the current vocabulary plus a sense of where the rough edges live.

Why .NET Core matters for .NET teams in 2026

Three working observations from the curation work:

  • The defaults moved. What used to be ceremony in older .NET projects is now scaffolded out of the box, but only if you start a new project. Most teams are not on the latest scaffold; that’s where .NET Core questions surface.
  • The community absorbed Azure-shaped opinions. A lot of .NET Core writing in the last 18 months has been “this is how we did it on Azure” with the surrounding pattern still applicable everywhere. Read for the pattern, not the cloud.
  • The toolchain rewards small upgrades. Most teams that pay down a single .NET Core debt every release end up months ahead of teams that wait for a “big rewrite”. The reading map below is biased toward those small upgrades.

The pieces below were curated because they keep coming up in real conversations: PRs, retros, code reviews, and the kind of question that lands in a Slack channel at 4pm on a Friday.

Reading map: start here

The first three issues are the ones to read in order. The rest are good as you need them.

1. Issue #451 - Common Challenges Developers Face with .NET Services and How

Start here (1 of 3). Common Challenges Developers Face with .NET Services and How. Issue #451 of .NET News Daily for May 8, 2026. (2026-05-08)

2. Issue #447 - I Rebuilt nanoGPT in C# So .NET Developers Can Understand LL

Start here (2 of 3). I Rebuilt nanoGPT in C# So .NET Developers Can Understand LL. Issue #447 of .NET News Daily for May 4, 2026. (2026-05-04)

3. Issue #445 - I Wasted 68 Minutes a Day Re

Start here (3 of 3). I Wasted 68 Minutes a Day Re. Issue #445 of .NET News Daily for Apr 30, 2026. (2026-04-30)

4. Issue #444 - Newtonsoft.Json vs System.Text.Json Which Should You Use in

Newtonsoft.Json vs System.Text.Json Which Should You Use in. Issue #444 of .NET News Daily for Apr 29, 2026. (2026-04-29)

5. Issue #443 - Serialization vs Deserialization in .NET

Serialization vs Deserialization in .NET. Issue #443 of .NET News Daily for Apr 28, 2026. (2026-04-28)

6. Issue #441 - Middleware in ASP.NET Core

Middleware in ASP.NET Core. Issue #441 of .NET News Daily for Apr 24, 2026. (2026-04-24)

7. Issue #440 - Stop juggling package managers, Source Generator

Stop juggling package managers, Source Generator. Issue #440 of .NET News Daily for Apr 23, 2026. (2026-04-23)

8. Issue #439 - ASP.NET Community Standup

ASP.NET Community Standup. Issue #439 of .NET News Daily for Apr 22, 2026. (2026-04-22)

9. Issue #436 - How to Build a Multi

How to Build a Multi. Issue #436 of .NET News Daily for Apr 17, 2026. (2026-04-17)

10. Issue #435 - Stop Repeating Yourself! Loops in C# (Part 10)

Stop Repeating Yourself! Loops in C# (Part 10). Issue #435 of .NET News Daily for Apr 16, 2026. (2026-04-16)

11. Issue #434 - Take full control of your floating windows in Visual Studio

Take full control of your floating windows in Visual Studio. Issue #434 of .NET News Daily for Apr 15, 2026. (2026-04-15)

12. Issue #431 - Beyond /health

Beyond /health. Issue #431 of .NET News Daily for Apr 10, 2026. (2026-04-10)

13. Issue #429 - C# Programming Language Guide

C# Programming Language Guide. Issue #429 of .NET News Daily for Apr 8, 2026. (2026-04-08)

14. Issue #428 - Entity vs DTO vs ViewModel in ASP.NET Core

Entity vs DTO vs ViewModel in ASP.NET Core. Issue #428 of .NET News Daily for Apr 7, 2026. (2026-04-07)

Looking for the rest? The full .NET Core archive lives on the .NET Core topic page.

Common pitfalls

Patterns we see across the curated archive when teams trip on .NET Core:

1. Treating .NET Core as a one-off project

The teams that handle .NET Core cleanly fold it into every release as small, ratcheting upgrades. Teams that defer it end up with a quarter-long tax. Several issues in the reading map above describe exactly this gap; the most recent one is a good five-minute read on the topic.

2. Reaching for a library before reading the standard library

The .NET BCL keeps absorbing what used to be third-party. Teams that stay on libraries from 2020 are paying for code the runtime now ships. Look at how recent issues handle the same problem with built-ins before you adopt a new dependency.

3. Skipping the test loop

If a .NET Core change does not have a test that fails before the change and passes after, you cannot trust the upgrade. The curated archive includes several walkthroughs of test setups that catch regressions early. Use them.

4. Confusing the documentation surface for the production surface

What works in a docs example often does not survive a production load profile. Read the curated issues for the post-mortem-flavored ones, not the marketing-flavored ones.

5. Underestimating the cost of un-tagged dependencies

A surprising number of .NET Core regressions in the curated archive came from a transitive dependency, not from the team’s own code. The fix is dull but worth doing once: pin versions, audit the dependency tree on each release, and treat indirect updates the same way you would treat direct ones. Several issues in the reading map walk through real-world examples of this exact pattern.

6. Skipping observability until production breaks

Teams that wait until .NET Core causes a customer-facing incident to add tracing or structured logs end up paying the worst version of that bill. The curated archive includes several walkthroughs of the cheapest observability slices that catch .NET Core regressions before they ship; they are listed under the observability topic.

FAQ

Q: I have never touched .NET Core. Where do I start? A: The first three entries in the reading map above are sequenced exactly for that. Read them in order; expect to spend an hour. Then bookmark the topic page and check it once a week.

Q: Does .NET Core change much between .NET versions? A: Yes. The patterns are stable but the defaults move. The curated archive is dated; read the most recent issue first to see the current shape, then read older issues for the why.

Q: How does .NET Core interact with the rest of the .NET stack? A: It depends on which slice you mean. The reading map above is intentionally cross-cutting: a few entries cover the runtime, a few cover the tooling, a few cover the libraries built on top. Pick the slice that matches your project today.

Q: I want to share this with my team. What is the one-page summary? A: This page. Send the link. The topic page is the deeper archive when they want more.

Q: What if a curated issue is out of date? A: Curated issues stay in the archive even when the underlying tech moves. The pillar page is updated quarterly to keep the order honest. If you spot a stale recommendation, reply to any issue and we will refresh.

  • C# - the working guide for the C# surface area.
  • ASP.NET Core - the working guide for the ASP.NET Core surface area.
  • Performance - the working guide for the Performance surface area.
  • EF Core - the working guide for the EF Core surface area.

Subscribe

Get the daily digest. Curated .NET Core issues land in your inbox the morning they go live. Subscribe to .NET News Daily.