Sources
Everything this workshop asserts is traceable. This page lists the community material we drew on, what state it was in when we checked it, and how far we are entitled to reuse it. No sources loaded.
Microsoft Learn, the .NET Blog, the language design notes and the runtime repositories are the only sources used for factual claims about behaviour, API shapes and support dates. Community material is here because it explains, benchmarks or pressure-tests those facts — never because it is the origin of them. Where a community post and Learn disagree, the entry is marked contradicts learn and we go with Learn.
Much of what has been written about .NET 11 and C# 15 dates from Preview 1–5. Union syntax and the memory-safety rules both changed before RC 1. Each Day 2 entry records the build it was written against so you can judge it. Treat any undated .NET 11 post as suspect.
Verification status and reuse tiers
Two independent axes. Verification is how much we trust it; tier is how much of it we are allowed to put on a slide.
| Status | What it means |
|---|---|
| verified | We read it and independently confirmed its central claims against Learn or by compiling the code ourselves. |
| partially verified | We read it and the main thrust holds up, but we did not check every claim. Fine for context; don't quote figures from it unchecked. |
| outdated | Was accurate, isn't any more — almost always preview drift. Kept when the reasoning is still instructive, with a note saying what moved. |
| contradicts learn | Actively disagrees with first-party documentation. Listed so you recognise the claim if you meet it in the wild, not because we endorse it. |
| unverifiable | Paywalled, video-only, or makes claims about internal behaviour we cannot reproduce. Read with the appropriate scepticism. |
| Tier | Permitted use in workshop material |
|---|---|
| 1 | Link to it and describe it in our own words. The default, and what almost every entry here uses. No copying of prose, figures, tables or code. |
| 2 | Restate a specific finding in our own words with an explicit citation on the slide. Used where someone else's benchmark or measurement is the point. |
| 3 | Short attributed quotation, 300 characters maximum, with author and link. Reserved for cases where the exact wording matters — a design-note rationale, for instance. |
This deck is built to be delivered inside someone else's organisation. Being able to point at the provenance and reuse basis of every third-party item is not pedantry — it is the difference between material you can hand over and material you cannot.
Adding a source
The registry is generated, not hand-edited. Anything added this way is validated before it can reach the page.
# Single link, straight into the registry with verification 'pending'
pwsh -NoProfile -File tools/add-source.ps1 `
-Url 'https://example.com/whats-new-in-ef-core-10' `
-Modules day1-m5 `
-Summary 'Walks through the complex-type mapping changes with a real model.'
# Validate, then regenerate site/assets/sources.js
pwsh -NoProfile -File tools/validate-sources.ps1
pwsh -NoProfile -File tools/build-sources.ps1add-source.ps1 normalises the URL and rejects duplicates, so the same
article arriving from two directions lands once. It captures only — nothing is
verified at intake, so the record lands as pending at reuse tier 1
(link only) and cannot reach the deck until a human vets it.
build-sources.ps1 ships verified records only, and refuses to emit anything
if validation fails.
Unique ids; every module id known; a reuse tier on anything marked verified; a
quote present only at tier 3 and never over 300 characters; a
writtenAgainst build recorded for every .NET 11 / C# 15 entry; and a
retrieved date on everything, because a source you checked a year ago is a
source you have not checked.