Should I worry about reigning in namespace number/length/scope?
Posted
by Jay
on Stack Overflow
See other posts from Stack Overflow
or by Jay
Published on 2010-04-01T20:07:50Z
Indexed on
2010/04/01
20:33 UTC
Read the original article
Hit count: 381
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.)
© Stack Overflow or respective owner