What good reasons are there for having the same namespace split across different assemblies?
I tend to like collecting types within a namespace, within the same compiled assembly - it makes things easy to find and references easy to manage. 

However, I have seen examples where the same namespace is split across projects and assemblies (in other words, in order to gain access to the complete namespace, you must reference multiple dlls). 

Can anyone give me some good reasons why you might want to arrange code this way?

thanks  
What good reasons are there for having the same namespace split across different assemblies?
===

I tend to like collecting types within a namespace, within the same compiled assembly - it makes things easy to find and references easy to manage. 

However, I have seen examples where the same namespace is split across projects and assemblies (in other words, in order to gain access to the complete namespace, you must reference multiple dlls). 

Can anyone give me some good reasons why you might want to arrange code this way?

thanks  