Is it a wrong to change namespace manually

Question

for organizational purposes I'm setting the namespace in every class manually.
like if I have an project called myProject namespace is myProject I change it to mySolution.myProject then changing nested directories the same way

namespace myProject.Folder1
{
     ///
}

to

namespace mySolution.myProject.Folder1
{
     ///
}

this way multiple projects can be parts of one namespace,
Is this a valid way to do this?

`project/properties/default namespace` ? – I4V Jul 15 '13 at 22:29 — I4V, Jul 15 '13 at 22:29
@I4V I didn't see this before :D Thanks. – Alaa Jabre Jul 15 '13 at 22:37 — Alaa Jabre, Jul 15 '13 at 22:37

score 1 · Answer 1 · answered Jul 15 '13 at 22:37

Changing the namespace is perfectly fine. Sometimes it can be advantageous to do so. If you are importing a large project into a smaller project, it might just make sense to change the smaller project over to the namespace conventions of the larger project.

One gotcha when doing this relates to web mark up files. .aspx/.ascx, not sure about MVC markups. I recall having the issue in MVC2. Improper references to namespaces here will not get caught by the debug compiler and will throw an error when trying to load the page. So if you do change the namespace of existing files, remember to change other source files that aren't checked by the compiler as well.

score 0 · Answer 2 · answered Jul 15 '13 at 22:30

Changing namespaces manually isn't a problem as long as you update any references to those namespaces.

ie in some other file you have;

using myProject.Folder1;

if that isn't updated to;

using mySolution.myProject.Folder1;

then you'll get compilation errors.

score 0 · Answer 3 · answered Jul 15 '13 at 22:33

0

I would use Refactor's rename option for this, just to be sure there aren't any references to the incorrect namespace somewhere. As far as using mySolution.myProject as a namespace, I don't see anything wrong with it.

answered Jul 15 '13 at 22:33

TOlsen

45
1
2
8

score 0 · Accepted Answer · edited May 23 '17 at 12:29

0

Changing the namespace from the default is pretty common. This stackoverflow question has a good answer about naming conventions:

namespace naming conventions.

Under your project properties, there is a setting on the Application tab where you can specify the default namespace. If you set that when you create your project, you won't have to manually change each class file as you create them.

edited May 23 '17 at 12:29

Community

1
1

answered Jul 15 '13 at 22:33

hatchet - done with SOverflow

15,919
5
47
57

Is it a wrong to change namespace manually

4 Answers4