2026-06 on Funky Si's Blog (Dev)

.NET 5 to 10: features per release

funkysi1701@gmail.com (funkysi1701) — Mon, 29 Jun 2026 18:00:00 +0000

Every November, .NET Conf brings a new major release of .NET. If you have been building on the platform since the early 2020s, you have watched the ecosystem move from “.NET Core” to a single, unified .NET — and pick up minimal APIs, Native AOT, Blazor full stack, Aspire, and a steady stream of C# language improvements along the way.

This post is a guided tour of what landed in each major version from .NET 5 through .NET 10. It is not exhaustive — Microsoft ships hundreds of changes per release — but it should help you remember which version introduced what, and where to dig deeper.

Version	Released	Support type	C# version	Status (June 2026)
.NET 5	Nov 2020	STS (18 months)	C# 9	End of support
.NET 6	Nov 2021	LTS (3 years)	C# 10	End of support
.NET 7	Nov 2022	STS (18 months)	C# 11	End of support
.NET 8	Nov 2023	LTS (3 years)	C# 12	Supported
.NET 9	Nov 2024	STS (2 years)	C# 13	Supported
.NET 10	Nov 2025	LTS (3 years)	C# 14	Current LTS
.NET 11	Nov 2026	Preview	C# 15	Preview Until Nov 2026 then STS

For the full release schedule and patch versions, see the official .NET releases documentation.

.NET 5 — November 2020

.NET 5 was the first release after the “Core” branding was dropped. Version 4.x was skipped deliberately so nobody confused it with .NET Framework 4.x. The message was clear: this is the main implementation of .NET going forward, not a side project.

Platform and runtime

Unified vision — one BCL and runtime targeting cloud, desktop, web, mobile, and IoT (the full unification completed in .NET 6).
Single-file applications and improved app trimming for smaller deployments.
ClickOnce publishing for .NET (Windows).
ARM64 support on Windows.
Performance work across the runtime, GC, and networking stack.

C# 9

C# 9 shipped alongside .NET 5 and brought several features that are now everyday tools:

Records — reference types with value-based equality and with expressions for non-destructive mutation.
Init-only setters — immutable object initialisation without verbose constructors.
Top-level statements — less boilerplate in small console apps.
Pattern matching — relational patterns (>, <, and, or, not) and improved switch expressions.
Source generators — compile-time code generation (the foundation for later JSON and logging generators).

Libraries and frameworks

EF Core 5 — split queries, table-per-entity (TPE) mapping, and Cosmos DB improvements.
ASP.NET Core in the 5.x line — gRPC improvements, HTTP/2 and HTTP/3 groundwork, and Blazor WebAssembly performance gains.
System.Text.Json — constructor and parameterised constructor support, [JsonIgnore] on properties, and better options for ignoring cycles.

.NET 5 reached end of support in May 2022. If you still have projects on it, plan an upgrade — there are no security patches.

.NET 6 — November 2021 (LTS)

.NET 6 delivered on the unification promise: one SDK, one base class library, and one runtime across mobile, desktop, IoT, and cloud. It was an LTS release and became the baseline many teams standardised on.

Developer experience

Hot reload in Visual Studio 2022 and dotnet watch — edit code and see changes without a full restart.
Minimal APIs — build HTTP APIs with far less ceremony than traditional controllers.
SDK workloads — optional components (MAUI, Blazor WebAssembly AOT, and others) install via dotnet workload instead of bloating the default SDK.
Project templates modernised — top-level statements, file-scoped namespaces, nullable reference types, and async Main in new projects.

C# 10

global using directives
File-scoped namespaces
Record structs
Improved interpolated strings and constant interpolated strings
AsyncMethodBuilder attribute for custom async method builders

Runtime and libraries

DateOnly and TimeOnly — separate date and time types without carrying a full DateTime.
PriorityQueue<TElement, TPriority> — a built-in min-heap.
System.Text.Json source generator, writeable JsonNode DOM, and IAsyncEnumerable serialisation.
HTTP/3 preview support via QUIC.
OpenTelemetry metrics APIs in System.Diagnostics.Metrics.
FileStream rewrite for better async performance on Windows.
Arm64 support for macOS (“Apple Silicon”) and Windows, with side-by-side x64 and Arm64 installs.

ASP.NET Core 6

Minimal APIs as a first-class style for microservices.
Blazor components renderable from JavaScript; AOT compilation for Blazor WebAssembly.
Improved gRPC and SignalR performance.

.NET MAUI

.NET Multi-platform App UI arrived in preview with .NET 6 — one codebase for Android, iOS, macOS, and Windows native apps. GA followed in 2022.

.NET 6 LTS ended in November 2024.

.NET 7 — November 2022

.NET 7 was a standard-term support release focused heavily on performance, cloud-native patterns, and polishing the developer experience. I wrote about upgrading to .NET 7 at the time — mostly smooth, with a few surprises around AutoMapper and EF Core triggers.

C# 11

Raw string literals — multi-line strings without escape-character pain.
required members — enforce initialisation at compile time.
Generic math — static abstract interface members for numeric generics.
List patterns — if (list is [var first, .., var last]).
UTF-8 string literals — u8 suffix for byte-oriented APIs.

ASP.NET Core 7

Rate limiting middleware — built-in protection against abuse.
Output caching — cache entire responses at the framework level.
Minimal API improvements — route groups, typed results, and filters.
Native AOT for console apps — smaller, faster-starting binaries (ASP.NET Core AOT came in .NET 8).

Performance and tooling

Continued JIT and GC improvements; Native AOT publishing matured.
Regex source generator for compile-time pattern compilation.
Library multi-targeting and package validation tooling for NuGet authors.

.NET 7 reached end of support in May 2024.

.NET 8 — November 2023 (LTS)

.NET 8 is the current-generation LTS baseline for many production workloads (supported until November 2026). It is the release where cloud-native tooling, Native AOT for web apps, and modern C# really clicked together.

C# 12

Primary constructors — declare constructor parameters on the type declaration.
Collection expressions — [1, 2, 3] syntax for arrays, spans, and lists.
Alias any type — using Point = (int X, int Y);
Default lambda parameters — optional parameters in lambdas.

ASP.NET Core 8

Blazor full stack — server-side rendering, streaming rendering, and enhanced interactivity models in one framework.
Native AOT for ASP.NET Core — ahead-of-time compilation for web workloads.
Keyed dependency injection — register and resolve multiple implementations of the same interface by key.
Frozen collections — optimised read-only collections for hot paths.
TimeProvider — abstract time for testable code.

.NET Aspire (now just called Aspire)

.NET Aspire launched in preview with .NET 8 — an opinionated stack for observable, distributed applications. AppHost orchestrates dependencies; ServiceDefaults wire up OpenTelemetry, health checks, and resilience. I have been using it for local microservice development and it removes a lot of port-and-connection-string drudgery. In 2025 .Net Aspire was rebranded to Aspire and version 13 was released (don’t ask why 13, but I believe it was so it was no longer tied to .NET releases)

Other highlights

EF Core 8 — complex types, primitive collections, JSON column mapping, HierarchyId.
NuGet Audit — warnings when packages have known vulnerabilities.
Windows Forms and WPF improvements — DPI, data binding, and hardware acceleration.
Source generators for COM interop and configuration binding.

.NET 9 — November 2024

.NET 9 continued the annual cadence with performance, AI integration, and polish across the stack. I covered several highlights in my .NET 9 post when it shipped.

C# 13

params collections — params works with Span<T>, ReadOnlySpan<T>, and collection types beyond arrays.
lock on System.Object — the lock statement can use more types safely.
Partial properties and indexers — split declarations across files.
Escape sequence \e for the ESC character.

Platform and libraries

Performance — runtime, GC, and JIT improvements across the board; the team publishes detailed benchmark posts each release.
AI abstractions — Microsoft.Extensions.AI packages unify access to language models and embeddings from different providers.
NuGet Audit defaults to reporting transitive dependency vulnerabilities (opt back to direct-only with <NuGetAuditMode>direct</NuGetAuditMode>).
OpenTelemetry enhancements and better observability defaults.

ASP.NET Core 9 and Blazor

MapStaticAssets() — fingerprinted, cache-friendly static files replace UseStaticFiles() for Blazor and modern web apps.
Blazor component state persistence, improved form handling, and better WebAssembly performance.
.NET Aspire 9 — dashboard improvements, deployment tooling, and more community integrations.

.NET 9 is standard-term support until November 2026.

.NET 10 — November 2025 (LTS)

.NET 10 is the current LTS release (supported until November 2028). If you are choosing a version for a new project in 2026, this is the long-term bet.

C# 14

Field-backed properties — use the field keyword when you outgrow auto-properties.
nameof for unbound generics — e.g. nameof(List<>).
Implicit Span<T> conversions — less ceremony at API boundaries.
ref/out/in in lambdas without explicit parameter types.
Extension blocks — static extension methods and properties in a dedicated syntax.
Null-conditional assignment (?.=) and user-defined compound assignment operators.

Runtime and libraries

JIT improvements — better inlining, devirtualisation, and loop inversion.
AVX10.2 support for SIMD workloads.
Native AOT enhancements and improved struct argument code generation.
JSON — stricter serialisation options, PipeReader support, duplicate property handling.
Post-quantum cryptography — expanded ML-DSA and related APIs.
WebSocketStream — simpler WebSocket usage; TLS 1.3 on macOS clients.

SDK and tooling

dotnet test integrates Microsoft.Testing.Platform.
Container images from console apps without a separate Dockerfile in simple scenarios.
dotnet tool exec for one-shot tool runs.
Native shell tab-completion scripts for the CLI.

ASP.NET Core 10 and Blazor

Blazor WebAssembly preloading and automatic memory pool eviction.
Passkey support for ASP.NET Core Identity.
OpenAPI and minimal API improvements.

One breaking change caught me when upgrading a Blazor WebAssembly app: HttpClient response streaming is enabled by default, which broke synchronous Stream.Read calls in generated API clients. I wrote about the fix in Blazor and .NET 10 — either opt out with <WasmEnableStreamingResponse>false</WasmEnableStreamingResponse> or move to async reads.

EF Core 10, MAUI, and desktop

EF Core 10 — named query filters, Cosmos DB improvements, and LINQ performance work.
.NET MAUI 10 — multi-file MediaPicker, WebView interception, Android API 35/36 support.
Windows Forms and WPF — continued quality and Fluent-style updates.

How to choose a version in 2026

Scenario	Recommendation
New production app, minimise upgrade churn	.NET 10 LTS
Existing app on .NET 8 LTS with no pressing need	Stay on 8 until you are ready; both 8 and 10 are supported
Experimenting with the latest features	.NET 9 or .NET 10 — check STS/LTS dates
Legacy maintenance	Upgrade anything still on 5, 6, or 7 — they are all end-of-life

Microsoft’s guidance has shifted over the years: LTS releases (6, 8, 10) alternate with STS releases (5, 7, 9) on an annual November cadence. STS now lasts two years; LTS lasts three. Remember there is no difference in quality between a LTS and STS release, it is only the support window that is different.

Portfolio: Azure, AI, and dev tools

funkysi1701@gmail.com (funkysi1701) — Mon, 22 Jun 2026 21:00:00 +0000

Featured Projects

Three live Azure workloads I own end-to-end — CI/CD static delivery, AI-backed search on real content, and full-stack Blazor with actual users.

🔧 Episode Atlas

Track TV progress at scale with per-user state and cloud-backed data.

What it does: Per-user episode lists, “last watched” markers, and curated metadata links — so long-running franchises stay manageable.

Tech used: .NET Blazor, Azure Static Web Apps, Azure Functions, Cosmos DB, GitHub auth.

Why it’s impressive: Demonstrates scalable data modelling and cloud-first architecture for user-driven applications.

Deployed to AzureImplements authentication / APIs / caching

Outcome: Turned a personal “where was I in 900+ episodes?” problem into a maintainable multi-tenant pattern for identity, persistence, and UX for ongoing shows.

Links: episodeatlas.com

🔧 Semantic Search

AI-powered natural language search for discovering content beyond keywords.

What it does: Accepts conversational queries, retrieves meaningfully related posts, and surfaces them alongside the site’s JSON index search.

Tech used: .NET, Azure, Cosmos DB, OpenAI.

Why it’s impressive: Showcases practical LLM integration in .NET beyond basic chat interfaces.

Deployed to AzureDesigned with clean architecture

Outcome: Explored how vector-style retrieval and operational concerns (cost, latency, content freshness) fit next to a static Hugo site without compromising the authoring workflow.

Links: search.funkysi1701.com · linked from Search

🔧 Blog Platform

Technical blog on Azure with CI/CD—fast static pages, search, and comments without babysitting an app server.

What it does: Publishes posts, generates RSS and a JSON search index, integrates Giscus for discussions, and deploys on every merge.

Tech used: Hugo, GitHub Actions, Azure Static Web Apps, Giscus.

Why it’s impressive: Highlights modern static-first architecture with automated deployment pipelines.

Deployed to AzureCI/CD via GitHub Actions

Outcome: Demonstrates a production-shaped static pipeline — preview builds, repeatable deploys, and content-driven SEO — suitable as a reference architecture for docs and marketing sites.

Links: GitHub repository

💼 Cloud & Production Systems

The featured trio — Episode Atlas, this blog (Hugo on Azure), and Semantic Search (search.funkysi1701.com ) — is fully described in Featured Projects above and not repeated here. Below is the rest of the catalogue by category.

🔧 Thorne Pentecostal Church

Dependable church presence online—clear for newcomers, simple for volunteers to keep current.

What it does — Presents service times, beliefs, and visitor information with a simple structure so members and newcomers get answers in one place.

Tech used — HTML/CSS, Azure Static Web Apps.

Why it’s impressive — Demonstrates proportionate engineering: production-grade static hosting and clear information architecture for stakeholders who need reliability, not complexity.

Engineering signals: Deployed to Azure · CI/CD via GitHub Actions

Outcome: Delivered a first web presence focused on clarity and sustainability so non-developers can keep content current with minimal process overhead.

Links: Thorne Pentecostal Church

🛠 Tools & Utilities

🔧 Mandelbrot Generator

Interactive Mandelbrot exploration in the browser—smooth zoom, pure WASM, zero server-side rendering cost.

What it does — Renders the Mandelbrot set in the client with zoom for desktop and mobile, demonstrating CPU-bound UI work in WASM.

Tech used — .NET Blazor WebAssembly, Azure Static Web Apps.

Why it’s impressive — Demonstrates client-side compute discipline in Blazor WASM: rich, interactive UI with predictable cost because heavy work never hits the server.

Engineering signals: Deployed to Azure · Designed with clean architecture

Outcome: Built the tool to stress-test interactive Blazor WASM performance and touch UX patterns — a small codebase that still informs decisions about heavier client-side workloads.

Links: Mandelbrot Generator

💡 Ongoing exploration

Areas I keep hands-on with outside these shipped projects:

.NET Aspire — Cloud-native composition and local dev parity
Kubernetes — Orchestration and service boundaries
Elasticsearch — Search and analytics stacks
Azure Functions — Event-driven and serverless patterns
DevOps automation — CI/CD, IaC, and release hygiene

🤝 Collaborate With Me

Interested in collaborating on a project or discussing an idea?

Contact Me — Get in touch
GitHub — Code and experiments
LinkedIn — Connect professionally

📚 More resources

Tools & Resources — Recommended development tools
About Me — Background and experience
Blog Posts — Technical writing

Stay visible when made redundant

funkysi1701@gmail.com (funkysi1701) — Mon, 22 Jun 2026 12:00:00 +0000

Sadly earlier this year I was made redundant from my Software Developer job. Looking for a new job has not been fun, but a few common themes have emerged that I wanted to share. My hope is that these will help others to put things in place that may help them in the future.

Go to events and meet people

Something I have said often is that I enjoy going to events or conferences, like NDC London . These are great places to hear interesting talks, however that is not all they are good for. When you are at a conference or user group you are in a room full of like-minded people, each of them has unique experiences of being a software developer.

I am not very good at networking, I tend to stand in the corner or look awkward. However the more of these events I go to the better I get. Even if you only talk to one new person, that is one more person that you have spoken to. Want an advantage in meeting people? Volunteer. If you are a volunteer at an event, you will need to interact with other people, you may need to help direct people or assist one of the speakers. I have found this gives me a tiny bit more confidence to go and start speaking with someone or ask a question. Check out my Volunteering at NDC

User Groups often have the same people coming week after week, take advantage of this and be one of those people as well. You will start to get noticed and remembered even if you barely speak to anyone. For me I don’t have any really local user groups, however I am enjoying spending time at LeedsSharp .

If you genuinely had a good conversation with someone, find them on LinkedIn (or other social media) and send them a quick “It was nice chatting with you” message, this helps solidify the connection and helps you remember it.

So far during this job search I have met a recruiter who I would not have met without going to events, I have had jobs suggested to me to apply for that I would not have received otherwise, and one hiring manager is someone I have met previously at an event.

Build a blog and write about what you are learning

Almost every interview I have had has featured a comment about my blog. Now building a blog is for the long game. If you are unemployed now and don’t have a blog this won’t help you today, but if you start one and write about your experiences a few times a year it may help you tomorrow.

Back in 2014 when I started blogging I wasn’t even a Software Developer, I was just an IT guy at a small company and I wanted to write about some of the cool things I was learning. I kept writing, some years I wrote more than others, there have been some big gaps where I didn’t write anything. But somehow I keep coming back to it and writing a short piece about a new version of X or a conference I have been to, or a trend that is happening.

My blog is a great talking point during interviews, it helps me talk about why I think sharing information with the community is so important, what technology I have used over the years, some of the things I have learnt. My blog is featured at the top of my CV, and hiring managers have said they love it.

When redundancy hit, refreshing my CV and LinkedIn was one of the first practical jobs I did: update the headline, add recent projects, link to the blog and projects page, and make sure nothing still implied I was in my old role. Mundane, yes — but recruiters and hiring managers check both before they ever speak to you.

Today blogging isn’t the only way you can share your ideas. You could create videos, start a podcast, or have an active social media channel. I think the key is consistency, if you do a lot of it, it can easily look impressive if you look back after a few years. I personally prefer the well written blog post that I can refer back to, or search for again and again.

Some ideas to get you started (but there are loads more):

What have you learnt today/this week
What do you think about technology X
How do you solve problem Y
Compare two approaches to the same problem
Your experience at a conference or meetup

Build side projects

Side projects are a great way to learn. You can create a side project with the goal of learning technology X, you can also blog about your journey, what problems you solved and what insights you gained from it.

I personally feel there is a lot of value from getting your side project into the wild and letting users interact with it. Users will find your edge cases and ask questions you hadn’t considered. Publishing onto the internet is not free so consider your architecture carefully.

What you can deploy depends on what you build. For simple websites you can do a lot with Github Pages or Azure Static Web Apps. For example this website is built with Hugo which is deployed to an Azure Static Web App for pennies per month. If you have more complex needs small Linux VMs can be created for not a lot more.

I have learnt more from running a side project in production than I have the original idea. Things like DNS, SSL certificates, authentication, SEO are all very important for running a project but they would have been missed if you only ever ran your side project on localhost. I think having a rounded experience gives you a leg up when it comes to talking about your skills in an interview scenario.

If you are between jobs, it is tempting to start something ambitious — the next big SaaS idea, a full-stack app with every feature you can think of. I have fallen into that trap myself. A small project you actually finish is worth more than a grand one that never ships. Pick something you can complete in a weekend or two: a CLI tool, a simple API, a static site, even a useful script. You will have something concrete to talk about in interviews, and the momentum of finishing one thing often makes the next one easier.

My personal side projects can be found on my projects page. My inspiration came from various places, my hobbies and interests, problems I am facing or hear about, or just stuff I want to learn.

Keep learning deliberately

Between applications there is often more waiting than interviewing. Use that time deliberately: look at the job descriptions you are targeting, spot a recurring skill gap, and focus on one thing rather than trying to learn everything. I listen to development podcasts on the commute and dip into courses — I have written before about using Pluralsight while doing the washing up. You will not become an expert in a fortnight, but being able to talk about what you are learning still comes up in interviews. For more general advice, see Tips for Developing Yourself .

Closing thoughts

Being made redundant is not something I would wish on anyone, and I am still in the middle of finding my next role. Some days the job search feels slow and frustrating. On the better days, I remind myself that the things I have been doing for years — showing up at events, writing on this blog, shipping side projects, keeping my skills current — are not wasted effort. They are what give me stories to tell in interviews and reasons for people to remember my name.

None of this replaces the practical side of job hunting: refreshing your CV and LinkedIn, talking to recruiters, applying properly, and working through the admin that comes with redundancy. I went through redundancy before, in 2021, and wrote about recruiters, interview rounds, and the spreadsheet I used to keep track of it all in my 2021 story . Visibility helps people remember your name; applications still get you in the door.

But small, consistent habits compound. You do not need to do everything at once. Pick one thing you can start this month: a user group, a blog post, a course on something job ads keep asking for, or a side project you can actually finish — Start Here collects a short reading path if you want inspiration from this blog first. Community work counts too; running a Code Club taught me as much about showing up as any meetup talk. If you still have a job but worry the ground is shifting beneath you, even better — start now while you have a bit more energy and headspace.

If you are going through something similar, I hope this helps. If you have found other things that worked for you, I would love to hear about them in the comments.

If you have enjoyed this article and want a monthly email with my latest posts, please sign up for my newsletter . You can also get in touch if you have questions or just want to chat.

Episode Atlas: track your Trek rewatch

funkysi1701@gmail.com (funkysi1701) — Mon, 01 Jun 2026 12:00:00 +0000

If you have ever tried to rewatch Star Trek properly—not just dip into a favourite episode, but work through hundreds of instalments across multiple series—you will know the feeling. You pause Deep Space Nine for a few weeks, start something else, and suddenly you have no idea which episode you were on. Spreadsheets help for a while, then they do not. Notes on your phone get lost. Memory is unreliable when you jump between TNG, DS9, and whatever new show has just dropped.

That is the problem Episode Atlas exists to solve: search 900+ episodes and films, mark what you have watched, and always know what to watch next—without treating a rewatch like a project-management exercise.

Why I built it

I write about Star Trek on this blog from time to time—episode reviews, top-50 lists, thoughts on new series. The honest origin is simpler than that, though: I wanted a better way to track my own rewatches.

Generic TV trackers are fine if you watch a bit of everything. They are less helpful when you care about one enormous franchise with inconsistent stardates, films mixed in with series, and the urge to jump to “all the Borg episodes” rather than the next sequential instalment. Episode Atlas is deliberately narrow (if you can describe a database of over 900 episodes and films narrow!): all of Star Trek, in one place, with features shaped by how fans actually rewatch.

You can use Episode Atlas without creating an account. Search the catalogue, open episodes, browse collections, and spin the random picker—no signup required.

When you want your progress to stick, sign in and start your captain’s log. Mark episodes watched, and the site remembers where you left off across every series—even if you detour from DS9 to TNG and back again.

Your service record

Once you are logging watches, the homepage gives you a service record at a glance: how many of the 900+ episodes you have seen, your percentage through the franchise, and your current watch rank (from the early ranks up through Lieutenant, Commander, and beyond). The site shows how many more episodes you need for the next rank, so a long rewatch feels like progress rather than a vague “I think I am halfway through Voyager.”

You can also earn commendations and build an active duty streak—small nudges to keep visiting when you are in the middle of a serious rewatch. It is the same idea as a fitness streak, but for Star Trek.

Find any episode in seconds

Search is the front door. Most visits start with “I know roughly what I want” or “which episode was that again?” Filter by series and season to narrow the list; keywords catch titles and descriptions you only half remember. Every series and the films are in one catalogue.

Episode pages: context and next steps

Open any episode and you get what you need for a rewatch session: metadata, previous and next navigation within the series, season progress, and actions to mark the episode watched or jump to the suggested next episode. Your captain’s log ties it together—what you logged today, what you have already seen, and where to pick up when you return.

The flow the site describes is simple: search → open → mark watched → move on. Three gestures, no spreadsheet.

Collections when you want a mood, not a season

Collections answer a different question from search: “It is late; show me something good in this mood.” Each collection points at Borg stories, time-travel episodes, holodeck highlights, and similar lists—fan knowledge encoded as browseable sets, so you skip filler without digging through every season.

Random episode when you cannot decide

The random episode picker is for the evenings when you and the sofa have agreed on Star Trek but not on which Star Trek. One click, one suggestion—useful when commitment is the hard part.

How it compares to other sites

Episode Atlas is not trying to replace Memory Alpha for lore or IMDb for cast lists. It is built for progress: what you have watched, what rank you have earned, and what to play next. If you have ever bounced between a wiki, a ratings site, and a generic tracker and still not known where you were in DS9, this is the gap it fills.

Try it

episodeatlas.com — free to browse, sign in when you want your captain’s log saved. Search, mark your first episode, and see your rank climb.

How do you track long rewatches—spreadsheet, app, or pure memory? If you try Episode Atlas, I would genuinely like to know what works for you and what does not: features you love, gaps that annoy you, or anything that would make a rewatch easier. Leave a comment below, or use the feedback option on episodeatlas.com —both reach me, and both help shape what I build next.

2026-06 on Funky Si's Blog (Dev)

.NET 5 to 10: features per release

.NET 5 — November 2020

Platform and runtime

C# 9

Libraries and frameworks

.NET 6 — November 2021 (LTS)

Developer experience

C# 10

Runtime and libraries

ASP.NET Core 6

.NET MAUI

.NET 7 — November 2022

C# 11

ASP.NET Core 7

Performance and tooling

.NET 8 — November 2023 (LTS)

C# 12

ASP.NET Core 8

.NET Aspire (now just called Aspire)

Other highlights

.NET 9 — November 2024

C# 13

Platform and libraries

ASP.NET Core 9 and Blazor

.NET 10 — November 2025 (LTS)

C# 14

Runtime and libraries

SDK and tooling

ASP.NET Core 10 and Blazor

EF Core 10, MAUI, and desktop

How to choose a version in 2026

Further reading

Official docs

On this blog

Portfolio: Azure, AI, and dev tools

Featured Projects

🔧 Episode Atlas

🔧 Semantic Search

🔧 Blog Platform

💼 Cloud & Production Systems

🔧 Thorne Pentecostal Church

🛠 Tools & Utilities

🔧 Mandelbrot Generator

💡 Ongoing exploration

🤝 Collaborate With Me

📚 More resources

Stay visible when made redundant

Go to events and meet people

Build a blog and write about what you are learning

Build side projects

Keep learning deliberately

Closing thoughts

Episode Atlas: track your Trek rewatch

Why I built it

Browse first, sign in to save

Your service record

Find any episode in seconds

Episode pages: context and next steps

Collections when you want a mood, not a season

Random episode when you cannot decide

How it compares to other sites

Try it