Package PSC.Analyzers.Blazor as a NuGet analyzer, publish it to a feed, and consume it across a solution including how to make rules fail the build.
Packaging, publishing and consuming Roslyn analyzers
Read More
Month: July 2026
Unit testing your analyzer
Test the PSC001 rule with Microsoft.CodeAnalysis.Testing: reference assemblies, inline diagnostic markup, and positive and negative cases.
Writing your first diagnostic
Write the PSC001 rule: a DiagnosticAnalyzer that finds Blazor [Parameter] properties and flags the ones that aren’t PascalCase.
Build a Roslyn Analyzer from scratch
Start a custom Roslyn analyzer for Blazor. We scaffold PSC.Analyzers.Blazor, explain every csproj setting, and set up analyzer release tracking.
I built a Visual Studio 2026 extension to bring back Blazor code-behind
Visual Studio 2026 dropped the built-in ‘extract @code to a code-behind’ feature. So I wrote a right-click extension that brings it back and handles the one tricky case that makes it hard.
