Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Refactoring with C#

You're reading from   Refactoring with C# Safely improve .NET applications and pay down technical debt with Visual Studio, .NET 8, and C# 12

Arrow left icon
Product type Paperback
Published in Nov 2023
Publisher
ISBN-13 9781835089989
Length 434 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Matt Eland Matt Eland
Author Profile Icon Matt Eland
Matt Eland
Arrow right icon
View More author details
Toc

Table of Contents (24) Chapters Close

Preface 1. Part 1: Refactoring with C# in Visual Studio FREE CHAPTER
2. Chapter 1: Technical Debt, Code Smells, and Refactoring 3. Chapter 2: Introduction to Refactoring 4. Chapter 3: Refactoring Code Flow and Iteration 5. Chapter 4: Refactoring at the Method Level 6. Chapter 5: Object-Oriented Refactoring 7. Part 2: Refactoring Safely
8. Chapter 6: Unit Testing 9. Chapter 7: Test-Driven Development 10. Chapter 8: Avoiding Code Anti-Patterns with SOLID 11. Chapter 9: Advanced Unit Testing 12. Chapter 10: Defensive Coding Techniques 13. Part 3: Advanced Refactoring with AI and Code Analysis
14. Chapter 11: AI-Assisted Refactoring with GitHub Copilot 15. Chapter 12: Code Analysis in Visual Studio 16. Chapter 13: Creating a Roslyn Analyzer 17. Chapter 14: Refactoring Code with Roslyn Analyzers 18. Part 4: Refactoring in the Enterprise
19. Chapter 15: Communicating Technical Debt 20. Chapter 16: Adopting Code Standards 21. Chapter 17: Agile Refactoring 22. Index 23. Other Books You May Enjoy

Building a Roslyn Analyzer code fix

Roslyn Analyzers allow you to provide options for users to automatically fix issues your analyzers detect in your code. They do this through something called a code fix provider, which can modify your document in an automated manner to resolve the diagnostic warning.

Think of it this way: diagnostic analyzers, like our OverrideToStringAnalyzer, help detect issues in your team’s code. On the other hand, code fix providers give you a way of fixing these issues.

Not all diagnostic analyzers will have code-fix providers, but in my experience, those that also provide code-fix providers tend to get addressed earlier and more consistently.

Let’s see how one works.

Creating a CodeFixProvider

First, we’ll add a new class to the Packt.Analyzers class library. We’ll call this class ToStringCodeFix. Replace its contents with the following code for a basic code fix:

using Microsoft.CodeAnalysis;
using Microsoft.CodeAnalysis...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image