Analyzing Code in .NET

on YouTube ↗50m

" summary

Shows that static analysis catches real bugs and speeds fixes by plugging analyzers into the editor: uses Roslyn compiler API and packages like MS.CodeAnalysis.NetAnalyzers and Sonar plus NUnit analyzers, demos IntelliTest surfacing a 366-day Zune hang, and writes a custom analyzer that flags calls to new Grid() and offers three code fixes — one replacing it with Grid.NewGrid fix which compiles cleanly in the Roslyn hive. Notes analyzer conflicts, a disabled disposable rule, and recommends treat warnings as errors and editorconfig to manage severities.

AI-written summary · about

" chapters (14)

1. 0:00Start
2. 1:09What Code Analysis Is
3. 14:21Intellitest
4. 16:13Code Reviews
5. 19:45Static Analysis Tools
6. 23:59Demo
7. 25:44Sonar Analyzer
8. 26:22Ide Analyzers
9. 30:04Treat Warnings as Errors
10. 33:03The Editor Config
11. 34:29Suppressing Configuration Options
12. 44:57Code Fixes
13. 45:12Build a Code Fix
14. 46:59Create an Extensibility Project

" related talks

• 01h 01mBuilding Code Analyzers with the new C# compiler platform (Roslyn)Filip W · NDC Sydney 2016
• 57mRoslyn: The Craft of Static AnalysisVladimir Panchenko · DotNext 2019 Moscow
• 54mContinuous Integration: Live Static Analysis using Visual Studio & the Roslyn APIEric Johnson · AppSecUSA 2016
• 53mEnforce Coding Standards in .NET: Overcome Broken Window SyndromeGael Fraiteur · JetBrains .NET Days Online 2024
• 01h 08mAnalyzing source code using RoslynErik Schierboom · NDC Oslo 2020
• 43mOvercoming Broken Window Syndrome Code Verification Techniques for NET DevelopGael Fraiteur · Build Stuff 2024
• 50mAutomate Yourself Out Of a Job With RoslynMark Rendle · Build Stuff 2020
• 01h 00mAutomate Yourself Out of a Job with RoslynMark Rendle · NDC Oslo 2021