Live Code Analysis and Squiggly Underlines

Visual Studio analyzes your code continuously as you type, not just when you build — those colored squiggly underlines are the visible result.

Red squiggles are errors — code that won't compile. Blue squiggles are typically suggestions or style violations. Green/other colors depend on your installed analyzers, but the pattern is consistent: hover any squiggle to see exactly what it's flagging, and press Ctrl+. on it to see available fixes (the same Quick Actions light bulb from an earlier course).

The Error List (View → Error List) aggregates everything in one place — every error, warning, and message across your entire solution, filterable and sortable, so you don't have to hunt through files one at a time to see what's flagged.

Roslyn analyzers are what actually power this. Roslyn is the .NET compiler platform, and analyzers are pluggable rules that run against your code in real time — some ship built into Visual Studio, others come from NuGet packages (a popular one: StyleCop.Analyzers for style consistency), and you can write custom ones for rules specific to your team.

Severity is configurable, not fixed. A given rule can be an Error (blocks the build), Warning (visible but doesn't block), Suggestion (a subtle underline), Silent (tracked but invisible), or None (off entirely) — configured per-rule, not all-or-nothing.

Why this matters for you

Squiggles catching a mistake while you type — instead of discovering it at build time, or worse, in code review — is one of the most genuinely time-saving habits in this whole track. Learning to read them instead of ignoring them pays off immediately.

▶️ Before the next lesson

Open the Error List (View → Error List) in your project and look at what's currently flagged, even if it's empty — you'll be intentionally adding a style violation in this course's hands-on lesson to see it appear.