Question

I run code analysis on a project and I get a warning saying

CA1020 : Microsoft.Design : Consider merging the types defined in {some namespace} with another namespace. {some namespace}

Why do I get this? Is there a negative implication of having too many namespaces?

Answer 1

I believe the main reason is discoverability and believe that plays a large part in the successful support and maintenance of your code. If it’s easier to discover it should be easier to maintain.

Here’s the a quote from MSDN.

Namespaces should
contain types that are used together
in most scenarios. When their
applications are mutually exclusive,
types should be located in separate
namespaces. Careful namespace
organization can also be helpful
because it increases the
discoverability of a feature. By
examining the namespace hierarchy,
library consumers should be able to
locate the types that implement a
feature