Versioning 1.0.1

on YouTube ↗01h 00m

" summary

Focuses on concrete versioning failures and fixes for C#/.NET: demonstrates how NodaTime 1.2.3 identity expectations break if binary vs source compatibility differs, shows optional-parameter and added-member changes can break compiled consumers despite semantic versioning rules, cites .NET SDK numbering (eg 2.2.201) and .NET Standard tie-ins, explains diamond dependency pains and a real-world plan where Google GAX → Google.Auth 1.0 forces major bumps, and proposes API lifecycle labels (experimental/alpha/beta/GA) plus NuGet package naming per API major.

AI-written summary · about

" chapters (5)

1. 0:00Start
2. 17:49Context
3. 25:23Compatibility
4. 40:07Dependencies
5. 48:39Network API versioning

" related talks

• 30mBreaking backwards compatibility: The easy way!Flavio Percoco · PyCon Australia 2015
• 01h 02mDesigning Wonderful .NET APIsJames Newton-King · NDC Sydney 2017
• 43mClient Library Design StoriesJon Skeet · Øredev 2018
• 42mASP .NET Basics for ExpertsLayla Porter · Øredev 2022
• 44mPut your C#, VB and F# projects and packaging on a dietDavid Gardiner · .NET Conf 2018
• 45m.NET Standard: The Easy Route to Platform IndependenceKathleen Dollard · Oredev 2017
• 43mOvercoming Broken Window Syndrome Code Verification Techniques for NET DevelopGael Fraiteur · Build Stuff 2024
• 22mHow to write better legacy code: A developer's wishlistBhaman Nikkahan · NDC Melbourne 2022