This post originated from an RSS feed registered with .NET Buzz
by Duncan Mackenzie.
Original Post: Jay Bazuzi discusses the 'Rename' Refactoring in some detail...
Feed Title: Code/Tea/Etc...
Feed URL: /msdnerror.htm?aspxerrorpath=/duncanma/rss.aspx
Feed Description: Duncan is the Visual Basic Content Strategist at MSDN, the editor of the Visual Basic Developer Center (http://msdn.microsoft.com/vbasic), and the author of the "Coding 4 Fun" column on MSDN (http://msdn.microsoft.com/vbasic/using/columns/code4fun/default.aspx). While typically Visual Basic focused, his blogs sometimes wanders off of the technical path and into various musing of his troubled mind.
If you haven't read much about Refactoring before, I'd suggest you check out Jay's earlier post on the subject, but he is now going into quite a bit more detail.
Whidbey Refactorings: Rename Let's start by talking about Rename. I view Rename as being one of the “Tier 1” refactorings – the refactoring we absolutely must provide, and which must be of the highest quality. They must be fast, reliable, and easy to use. You’re going to use them often, and we want you to like them a lot...