Use your source code to document your application
summary
Shows how Roslyn parses .NET projects into syntax trees and semantic models, loads solutions via MSBuild or Buildalyzer, and extracts types, commands, events and handlers into a compact JSON intermediate (about 30–60s JSON extraction for a solution). Demonstrates generating Markdown/AsciiDoc and diagrams with PlantUML and Mermaid, detects branching, sagas, missing handlers and inherited fields, and uses the Pitstop sample app to prove the pipeline creates readable, up-to-date docs and sequence/aggregate diagrams that match real code paths.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 1:09Session goals
- 3:40Audience needs
- 4:44Documentation challenges
- 6:57AI impact on docs
- 7:18Existing docs solutions
- 10:10Specification by example
- 13:10Docs tool limitations
- 15:11Roslyn introduction
- 18:07Syntax trees with Roslyn
- 23:45Semantic analysis
- 29:13Syntax walkers
- 33:20Workspaces in Roslyn
- 35:31Tailoring documentation to project needs
- 36:35Markdown and AsciiDoc
- 38:25Living Documentation tool
- 40:37Pitstop case study
- 42:03JSON from code analysis
- 44:56Commands and events
- 46:29Handler mappings
- 49:18Markdown from code
- 51:07Sequence diagrams
- 53:16Aggregates and relationships
- 54:21Docs in build pipelines
- 56:07State machines and sagas
- 57:56AsciiDoc from attributes
- 59:01Cross-language docs
- 59:45Alternative visualizations
- 1:00:27Summary and call to action
related talks
01h 00mUse your source code to document your application
01h 00mUse your source code to document your application
01h 08mAnalyzing source code using Roslyn
01h 16mAutomate yourself out of a job with Roslyn
01h 00mAutomate Yourself Out of a Job with Roslyn
01h 01mWriting Code with Code: Getting Started with the Roslyn APIs
30mRoslyn for teamlead.If something takes more than 5 minutes -write a script.
55mCode that writes code - .NET Source generators