Why editor config ?
summary
Uses .editorconfig to centralize and enforce style and analyzer rules across editors and CI, tying Visual Studio settings to file rules so team preferences follow projects. Demonstrates three in‑IDE fixes: Ctrl+E D for format, Ctrl+K E for code cleanup, Ctrl+. for code fixes backed by Roslyn analyzers. Shows dotnet‑format CLI for solution wide fixes, explains editorconfig templates (.NET vs empty), how severities map to warnings or build‑breaking errors, and how rules are inherited or rooted in folder scopes.
AI-written summary · about
chapters (28)
- 0:00Start
- 0:04Jerry Nixon
- 2:05Code Quality
- 2:22Categories of Code Quality
- 4:05Naming Conventions
- 4:23Reliability
- 6:13Formatting
- 7:03Miscellaneous Rules
- 8:33Documentation
- 10:05Code Formatting inside Visual Studio
- 11:34Code Cleanup
- 12:59Three Ways I Can Update My Code
- 13:36Easiest Way To Interact with Visual Studio
- 17:51Cleanup
- 19:01Click Cleanup
- 20:32Apply Header File Preference
- 20:48Code Fix
- 23:44Netformat
- 24:35Export all of Your Settings in Visual Studio
- 29:08Let Editor Config Override My Local Settings
- 29:41Control the Way Analysis Works
- 31:26Generate and Edit Config
- 32:24Enforce Code Style
- 34:16Codeanalysis Net Analyzer
- 37:38Analyzer Configuration
- 37:57Can I Add More Analyzers
- 40:26Analyzers
- 42:30Why Would You Use Editor Config
related talks
37mIncrease your .NET Productivity Tips & Tricks in Visual Studio 2019
31mCode Style and Violence
44mUsing Visual Studio Code as Your Default PowerShell Editor
59mUnleash the Power of Visual Studio Code
50mAnalyzing Code in .NET
01h 14mVisual Studio Tips & Tricks
38mHow to be productive developing with .NET on a Mac
23mFast Focus: Sneak Peek at How Visual Studio's Code Editor Works Under the Hood