Build great libraries using .NET Standard
summary
Recommends start with .NET Standard 2.0 as the best tradeoff for reach and API richness, shows converting a .NET Framework library to .NET Standard, using the Windows Compatibility Pack (~27,000 APIs) when needed, and adding the analyzer that surfaces unsupported platform calls as warnings or build errors. Demonstrates multi-target with TargetFrameworks to produce per-platform binaries inside one NuGet, automated packaging via SDK props, Nerdbank.GitVersioning for automatic versions, Directory.Build.props/targets for central package versions, and guidance on strong‑naming and automatic binding redirects.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:40What is NET Standard
- 6:36Demo project
- 8:07Package references
- 8:46Default settings
- 10:26Calling Registry API
- 11:53Warnings
- 13:14Package
- 14:03Wrapper
- 15:35WP Library
- 16:51Switching branches
- 18:06Switching context
- 19:06Multiple packages
- 20:26Best practices
- 22:24Elephant in the room
- 24:31Strong naming
- 27:01Binding redirects
- 32:08Versioning
- 41:23MSBuild
- 44:13Summary
related talks
45m.NET Standard: The Easy Route to Platform Independence
52mWhat is .NET Standard?
01h 01mWhat is .NET Standard?
53mThe .NET standards for Dummies
54mPorting MVVM Light to .NET Standard: Lessons learned
01h 04mWhat is new in .NET 6 and the future of .NET
46mWhat do I do with my old .NET Framework Apps?
01h 03mAn independent look at the arc of .NET