in 2002, too). But it only renames the project itself, doesn't rename
"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
For a task that is so obvious, so frequent, and so necessary, it amazes me
that VS *still*
does not make this easy. Most of us who have experience know how to do
the massive
search-and-replace (my text editor has a replace-in-files feature which is
really
convenient for this), but it is tedious, and it's hard to explain all the
details to
someone who hasn't already done it.
joe
On Sun, 10 Feb 2008 22:30:07 GMT, "David Ching"
<dc@remove-this.dcsoft.com> wrote:
"Ajay Kalra" <ajaykalra@yahoo.com> wrote in message
news:5F92BFAA-8358-4C3A-9589-D8D9E85688C9@microsoft.com...
I always name it what I want. I do it at a temporary location though. If
it turns out to be what I want, I simply move it to the folder where I
want it to be.
Also, I dont hestitate to start a new project and add new files with the
same content as the temp project with good use of clipboard.
Well, the project name can change several times throughout development.
Some of the codenames have changed, even. It bothers me to see files and
classes called COldCodenameDocument, so I regularly do use Search and
Replace to make it CNewCodenameDocument. And the same for the View, etc.
The 20 minutes it takes to do this is much saved over the lifetime of the
project to avoid confusion of the team and explaining a thousand times the
history of the codenames to new hires....
There really should be a project refactoring that allows easy change of
the
project name.
-- David
Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm