Continuous Integration: Live Static Analysis using Visual Studio & the Roslyn API
summary
Shows how to use the Roslyn API and Visual Studio 2015 to write live static rules, and delivers a free extension published as a PumaScan NuGet with about 40 rules that runs in the IDE and under MSBuild. Scanning a demo app raises 64 warnings, about 54 true positives and ~10 false positives; rules flag weak password length, SQL injection patterns, unvalidated redirects and config issues. Built extension works, but additional-file diagnostics need project tweaks and double‑click navigation is not yet supported.
AI-written summary · about
chapters (21)
- 0:00Start
- 4:58Web Config Analyzer
- 6:22Mini Code Review
- 12:56Rosalind Api
- 15:41Syntax Visualizer
- 16:54The Syntax Visualizer
- 17:05Identity Config File
- 20:07Diagnostic Analyzer Class
- 21:19Step Two
- 22:39Syntax Analyzer
- 22:59Invocation
- 23:34Password Length Analyzer
- 30:18Non Code Files
- 33:43Getting the Additional File To Show Up
- 37:08Debug Compilation
- 40:49Install the Puma Scan Extension
- 48:33Stats
- 49:16Dataflow
- 50:17Future Enhancements
- 51:17Suggested Code Fixes
- 52:04Acknowledgments
related talks
57mRoslyn: The Craft of Static Analysis
50mAnalyzing Code in .NET
01h 00mAutomate Yourself Out of a Job with Roslyn
30mRoslyn for teamlead.If something takes more than 5 minutes -write a script.
36mCode Analysis: Empowering developers to write performant, reliable, and safe C++
53mEnforce Coding Standards in .NET: Overcome Broken Window Syndrome
01h 16mAutomate yourself out of a job with Roslyn
01h 08mAnalyzing source code using Roslyn