Book Image

Refactoring with Microsoft Visual Studio 2010

By : Peter Ritchie
Book Image

Refactoring with Microsoft Visual Studio 2010

By: Peter Ritchie

Overview of this book

Changes to design are an everyday task for many people involved in a software project. Refactoring recognizes this reality and systematizes the distinct process of modifying design and structure without affecting the external behavior of the system. As you consider the benefits of refactoring, you will need this complete guide to steer you through the process of refactoring your code for optimum results.This book will show you how to make your code base more maintainable by detailing various refactorings. Visual Studio includes some basic refactorings that can be used independently or in conjunction to make complex refactorings easier and more approachable. This book will discuss large-scale code management, which typically calls for refactoring. To do this, we will use enterprise editions of Visual Studio, which incorporate features like Application Performance Explorer and Visual Studio Analyzer. These features make it simple to handle code and prove helpful for refactoring quickly.This book introduces you to improving a software system's design through refactoring. It begins with simple refactoring and works its way through complex refactoring. You will learn how to change the design of your software system and how to prioritize refactorings—including how to use various Visual Studio features to focus and prioritize design changes. The book also covers how to ensure quality in the light of seemingly drastic changes to a software system. You will also be able to apply standard established principles and patterns as part of the refactoring effort with the help of this book. You will be able to support your evolving code base by refactoring architectural behavior. As an end result, you will have an adaptable system with improved code readability, maintainability, and navigability.
Table of Contents (17 chapters)
Refactoring with Microsoft Visual Studio 2010
Credits
About the Author
Acknowledgement
About the Reviewers
Preface
6
Improving Class Quality
9
Improving Architectural Behavior

You ain't gonna need it


"You ain't gonna need it" (or YAGNI for short) is a principle that gained an established foothold in the Extreme Programming community. The principle centers around the tendency of some software to increase functionality for reasons other than the features. "Featuritis" the symptom of some software to increase features simply to satisfy a check-list or some market collateral is related to you ain't gonna need it.

"You ain't gonna need it" gives us a criteria by which to focus our refactoring efforts. If we know we don't need a particular feature, we can make better decisions about what may or may not be dead code. Code that supports a particular feature, for example, that we don't need will become dead code if we decide we ain't gonna need that feature.

Code in a code base that supports a feature that isn't needed, or performs actions that "might be needed in the future" increases the amount of code that needs to be read. In order to effectively evolve a code base...