PacktLib: Refactoring with Microsoft Visual Studio 2010

Refactoring with Microsoft Visual Studio 2010

About the Author

Acknowledgement

About the Reviewers

Introduction to Refactoring

What is refactoring?

Why the term refactoring?

Unit testing the second half of the equation

Simple refactoring

In the software development trenches

The option of rewriting

Working refactoring into the process

What to refactor

Refactoring in Visual Studio® 2010

Improving Code Readability

Built-in Visual Studio® refactorings

The smell of code

Intention-revealing design

You ain't gonna need it

Keeping track of code changes

Removing unused references

Improving Code Maintainability

Code maintainability

Improving Code Navigation

Navigating object-oriented code

Convention over Configuration

Navigation with design patterns and principles

Improving Design Correctness

Liskov substitution principle

Composition over inheritance

Object-oriented design and object behavior

Move initialization to declaration

Improving Class Quality

Refactoring to Loosely Coupled

What is loosely coupled?

Dependency Inversion principle

Inversion of Control

Dependency Injection

Working with IoC containers

Decorator pattern

Detecting highly-coupled

Types of coupling

Interface segregation principle

Drawbacks of loosely-coupled

Other methods of loose-coupling

Refactoring to Layers

Model View Presenter (MVP)

Additional layers

Improving Architectural Behavior

Behavioral patterns

Improving Architectural Structure

Structural patterns

Object/Relational Mapping

Ensuring Quality with Unit Testing

Change is not always good

Automated testing

Mocking frameworks

Unit testing existing legacy code

Unit testing in Visual Studio®

Test driven development

Unit testing frameworks

Automating unit-testing

Third party refactoring tools