I am working with multiple websites (freelancer) and a good amount of them I write using C# MVC4.

I created a very good boilerplace project that I plan to use on every next starting mvc4 application I build, however the namespace is named Website. I also do a lot of copy-paste from one project to another and then I always have to refactor namespaces, if I will use single namespace (Website) on all my websites then this problem dissapears.

However - will this somehow impact my application, is it considered a very bad practice?

closed as primarily opinion-based by durron597, user40980, gnat, Ixrec, user22815 Aug 29 '15 at 22:57

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.


The namespaces should be a little more meaningful than that. If you have some general purpose classes for processing CSV files, maybe use the namespace Qmal.CSVUtil. This makes it easier and less confusing to reuse that code later in other (possibly non-website) projects. You might have some other general purpose web-site related classes that could be reused in other web projects, so maybe use the namespace Qmals.GeneralWebStuff but something simpler such as Qmal.Website might actually be OK for that. Then there's the stuff that's very project specific, and for that you can use a namespace such as Client3.WebProject.

Not the answer you're looking for? Browse other questions tagged or ask your own question.