Comments on: Refactoring: Removing duplication more safely

By: Small step refactoring: Overload constructor at Mark Needham

Small step refactoring: Overload constructor at Mark Needham — Thu, 17 Jun 2010 00:27:14 +0000

[...] previously written about some approaches that I've been taught with respect to taking small steps when refactoring code and another approach which a couple of colleagues have been using recently is the idea of [...]

By: Safe refactoring: Removing object initializer, introducing builder at Mark Needham

Thu, 25 Jun 2009 14:25:16 +0000

[...] previously wrote about an approach we took to safely remove some duplication and I recently followed a similar mantra to replace an object initializer call which had around 40 [...]

By: DotNetShoutout

DotNetShoutout — Tue, 26 May 2009 14:20:06 +0000

Refactoring: Removing duplication more safely – Mark Needham…

Thank you for submitting this cool story – Trackback from DotNetShoutout…

By: Andy Palmer

Andy Palmer — Tue, 26 May 2009 07:55:26 +0000

Another method could be to change the implementation of the old class to delegate to the new class.
You should then be able to Inline Class on the old class to replace all references.

By: Reflective Perspective - Chris Alcock » The Morning Brew #354

Reflective Perspective - Chris Alcock » The Morning Brew #354 — Tue, 26 May 2009 07:40:45 +0000

[...] Refactoring: Removing duplication more safely – Mark Needham talks about a technique he used when refactoring and removing code recently, with the aim of making it easier and safer to remove duplicated code. [...]