--
( OHM ) - One Handed Man
AKA Terry Burns - http://TrainingOn.net
"_DD" <_DD@nospam.com > wrote in message
news:6qvg32lujl 6rjufhalvt40hnh 5l455a3td@4ax.c om...[color=blue]
> Is there any easy way to rename an entire project? I'd like to change
> everything: folder, sln file, etc.
>[/color]
What do u mean with "easy"? Rename folder, .sln, .cproj and contend of these
files manually
_> Is there any easy way to rename an entire project? I'd like to
_> change everything: folder, sln file, etc.
_>
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour
"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
On Sun, 9 Apr 2006 07:13:47 +0000 (UTC), Michael Nemtsev
<nemtsev@msn.co m> wrote:
[color=blue]
>What do u mean with "easy"? Rename folder, .sln, .cproj and contend of these
>files manually
>
>_> Is there any easy way to rename an entire project? I'd like to
>_> change everything: folder, sln file, etc.[/color]
Renaming those would be easy, but I'm not clear on how the internals
would still work. For instance, the renamed .sln and .cproj files
would still have internal references to the old folder and file names,
right?
Even hand-editing the VS project files would be no big deal (presuming
they are in Ascii format), but if there's a chance that anything could
get screwed up, it wouldn't be worth it.
I guess an appropriate followup question would be: Which files contain
references and dependencies?
"_DD" <_DD@nospam.com > wrote in message
news:7mgj32lgkg esh1gric0693lm5 m8tptmjpj@4ax.c om...[color=blue]
> On Sun, 9 Apr 2006 07:13:47 +0000 (UTC), Michael Nemtsev
> <nemtsev@msn.co m> wrote:
>[color=green]
>>What do u mean with "easy"? Rename folder, .sln, .cproj and contend of
>>these
>>files manually
>>
>>_> Is there any easy way to rename an entire project? I'd like to
>>_> change everything: folder, sln file, etc.[/color]
>
> Renaming those would be easy, but I'm not clear on how the internals
> would still work. For instance, the renamed .sln and .cproj files
> would still have internal references to the old folder and file names,
> right?
>
> Even hand-editing the VS project files would be no big deal (presuming
> they are in Ascii format), but if there's a chance that anything could
> get screwed up, it wouldn't be worth it.
>
> I guess an appropriate followup question would be: Which files contain
> references and dependencies?[/color]
On Mon, 10 Apr 2006 05:51:07 +0100, "OHM \( One Handed Man \)"
<me@mine.com> wrote:
[color=blue]
>The point is there is no single step to do the folder, solution, project
>etc. But the individual renaming is as you say simple.[/color]
I'm still not following. If you rename original.sln to modified.sln,
the internal references would still point to original.* files. You'd
have to modify all those internal references. How is that
accomplished? Is it safe to simply edit the .proj and .sln files with
a text editor?
>> Is it safe to simply edit the .proj and .sln files with[color=blue][color=green]
>> a text editor?[/color][/color]
Hi _DD,
Yes, it is safe and pretty simple, provided you do it sensibly.
Assuming you have a solution named "Useful.sln ", containing a project
called
"Use.vbproj ". You changed the Solution name to "Useless.sl n" and the
Project name to
"Misuse.vbproj" , then :
1. The .sln file contains the reference to the .vbproj file, so you
would need to open it in
notepad and change the line that says :
--------------
Project("{some GUID}") = "Use", "Use.vbproj ", "{some GUID}"
EndProject
--------------
Change "Use" to "Misuse".
2. The .vbproj file contains references to everything you have added to
your project, including forms, folders and other files. It is in XML
format, so you just need to edit the nodes under <Files><Include > to
make appropriate changes for each folder / file name that has been
changed.
Good response, unfortunately the OP wanted ( I think ) almost a single point
to do all the renaming and its not there; as you point out it equires
severals steps.
"Cerebrus" <zorg007@sify.c om> wrote in message
news:1144996178 .528763.261710@ i40g2000cwc.goo glegroups.com.. .[color=blue][color=green][color=darkred]
>>> Is it safe to simply edit the .proj and .sln files with
>>> a text editor?[/color][/color]
>
> Hi _DD,
>
> Yes, it is safe and pretty simple, provided you do it sensibly.
>
> Assuming you have a solution named "Useful.sln ", containing a project
> called
>
> "Use.vbproj ". You changed the Solution name to "Useless.sl n" and the
> Project name to
>
> "Misuse.vbproj" , then :
>
> 1. The .sln file contains the reference to the .vbproj file, so you
> would need to open it in
> notepad and change the line that says :
> --------------
> Project("{some GUID}") = "Use", "Use.vbproj ", "{some GUID}"
> EndProject
> --------------
> Change "Use" to "Misuse".
>
> 2. The .vbproj file contains references to everything you have added to
> your project, including forms, folders and other files. It is in XML
> format, so you just need to edit the nodes under <Files><Include > to
> make appropriate changes for each folder / file name that has been
> changed.
>
> HTH,
>
> Regards,
>
> Cerebrus.
>[/color]
Actually my response was only an effort to answer _DD's last post :
[color=blue][color=green]
>> If you rename original.sln to modified.sln,
>> the internal references would still point to original.* files. You'd
>> have to modify all those internal references. How is that
>> accomplished? Is it safe to simply edit the .proj and .sln files with
>> a text editor?[/color][/color]
I completely agree, that it is a multi-step process. And referring to
his original post, "easy" is a term that may mean different things to
different people. ;-)
"Cerebrus" <zorg007@sify.c om> wrote in message
news:1145017370 .467791.305690@ z34g2000cwc.goo glegroups.com.. .[color=blue]
> Hi Terry (OHM) (One Handed Man),
>
> Thanks for the encouraging words...
>
> Actually my response was only an effort to answer _DD's last post :
>[color=green][color=darkred]
>>> If you rename original.sln to modified.sln,
>>> the internal references would still point to original.* files. You'd
>>> have to modify all those internal references. How is that
>>> accomplished? Is it safe to simply edit the .proj and .sln files with
>>> a text editor?[/color][/color]
>
> I completely agree, that it is a multi-step process. And referring to
> his original post, "easy" is a term that may mean different things to
> different people. ;-)
>
> Regards,
>
> Cerebrus.
>[/color]
Comment