Change Default Namespace when creating Class in Folder (Visual Studio)

Solution 1:

There are 4 schools of thought here:

• edit it manually
• live with it
• change the class template (or export a second class template)
• create the file outside the sub-directory, then drag it in

I tend to use the 4th; it is quicker than editing, and less hassle than changing the templates

Solution 2:

To change the default namespace:

Right click on the project, go to properties and under the 'Application' tab there is a 'Default namespace' field.

Note that this doesn't answer your exact question though, it depends on your folder. You basically you need to rename that folder to 'Model'.

Solution 3:

If you have ReSharper installed, right click on the folder in your solution you want to be excluded from namespaces and select properties. In the properties pane, select False for Namespace Provider and that will make Visual Studio ignore the folder when generating namespaces in new files.

Solution 4:

If you already have one class under that folder with the desired namespace. You could take advantage of the Move type to ClassName.cs light bulb suggestion.

For example, you created Order.cs with the correct namespace MyCompany.MyProject.Domain.Model under the Extensions folder. If you want to add Trace class you do it like so:

Ctrl + . when the edit cursor is anywhere around the class Trace words will show the suggestion.

so... Ctrl + . Down Down Enter

Result:

Solution 5:

Resharper has changed how they do this (as of VS2017).

1. Add your folder.
2. Add your first class.
3. Manually alter the namespace to be what you want. (Usually that's removing the last piece from the namespace that represents the folder the class is in.)
4. The namespace will now be underlined to say that it doesn't match the folder structure. Click on the the options to fix it, and select "Folder '...' do not introduce namespace".

Now your folder is set to expect the namespace for all new classes. However, when you add a new class to the folder, it now complains that it's not the namespace that you set it to in step #3 above.

So, you still need to manually alter the namespace, but at least resharper isn't trying to fight you anymore.