Renaming Project / Solutions

  • Thread starter Thread starter Chris Marsh
  • Start date Start date
C

Chris Marsh

How does one go about renaming a project and/or solution for VS.Net C#? I
have had corruption and needed to rebuild the project file-by-file without.
I have compiled, renamed, etc., but there must be an easier way or a Q that
gives us step-by-step instructions.

Thanks
 
Are you recanaming the files by right click and select 'rename'? Have you tried using the F2 key after you selected the file? Or left click the file two seconds after you have selected the file? A wizard will probably ask you to do the same thing. But maybe in a dialog box rather than in the 'Solution Explorer'

HT

----- Chris Marsh wrote: ----

How does one go about renaming a project and/or solution for VS.Net C#?
have had corruption and needed to rebuild the project file-by-file without
I have compiled, renamed, etc., but there must be an easier way or a Q tha
gives us step-by-step instructions

Thank
 
I found out that I can rename the project and solution by right-clicking
however what about the Assembly Name, Default Namespace. Renaming those is
possible inside of the property pages but what negative or downsides are
there. Everything appears to have gotcha's....


one said:
Are you recanaming the files by right click and select 'rename'? Have you
Click to expand...
tried using the F2 key after you selected the file? Or left click the file
two seconds after you have selected the file? A wizard will probably ask you
to do the same thing. But maybe in a dialog box rather than in the 'Solution
Explorer'.
 
Hi Chris,

As you've mentioned that the "Assembly Name" and "Default Namespace" are
all able to be modified by the project's property window.(Right click the
project and select the properties menu item). In addition, the setting in
the VB.NET project ans C# project are quite different.
1. In C# project, we have the "Default Namespace" setting which indicate
the default namespace of the businsess component to use. And we can't
change all the pages or components' namespace in the c# project by changing
this value because the namespace of each codebehind or a class is
explicitly declared in each cs file. So we need to be careful before
changing the "default namespace" because, it'll make you encounter some
error because the default namespace be changed and some business component
you called can't be found(their namespace remain the old one).

2. In VB.NET project, when we opened the .vb or aspx.vb file, we can see
that the namespace is not explicitly specified in it. Thus, it make us
possbile to set the namespace for the whole project in the project's
properies window.

Hope helps.


Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx
 
Hi Chirs,

Have you had a chance to check out the suggestions in my last reply or have
you got any ideas on this issue? If you have anything else unclear or have
any new ideas, please feel free to post here. Thanks.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx
 
I have, I can rename just about anything however it appears that I have
problems after doing that. Is there a special process that should be
followed?

thanks for the reply.
 
Hi Chris,

As far as I know, there isn't any special process which are forced to do
when renaming a project. However, since the refactor function of the
VS.NET's current version hasn't been strong enough maybe some of your
existing pages source or some other component in the porject need manual
modified. In addition, what's the problem you encounter now? Thanks.


Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx
 
It completely died after I did it so I haven't tried again...needed to get
the project done:) I will try it tomorrow and see what happens.

Also, I have another thread that you are addressing...any thoughts there?

Chris
 
Back
Top