It's worth noting that the XNA framework only has (not counting the content pipeline DLLs) two DLLs: the main framework and one for the Game class and related classes. They don't have a separate DLL for each namespace.
I went through a phase where I too wanted lots of DLLs for whatever reason. What I quickly learned is that it becomes hard to do that without running into these problems:
- My DLLs all wound up relying on functionality from the other ones. So what's the point of splitting them up if each requires the others?
- I generally wanted to use the functionality from all of them in a game which just meant more work to add a lot of references.
- It's kind of annoying to have a ton of projects.
In the end I just went back to building my entire framework into a single DLL. It's compact, simple, and makes sense. Unless you have good reason to split up multiple DLLs, I highly recommend not doing so.
