Should I worry about reigning in namespace number/length/scope?
- by Jay
I've recently reorganized a solution-in-progress from 24 projects to 4.
To keep the copious files organized in the "main" project, things are in folders in folders in folders. I think I've preserved a logical, discoverable arrangement of the solution content.
As a result, of course, I end up with namespaces like AppName.DataAccess.NHibernate.Fluent.Mappings.
Is there any compelling reason that I should care about flattening out the namespace hierarchy when my project has a somewhat deeply nested folder structure?
(I am not concerned about resolving or managing using directives; I let ReSharper do all the heavy lifting here.)