Organisation of namespaces by project

[Mr Flibble]

If you have the namespaces

foo.bar.x
foo.bar.y
foo.bar.z

You could put these all in one project called foo.bar or you could
create a project for each. I've just realised that I have quite a few
project files in my solution and I was wondering if this is normal?
Especially since they're all under the same common namespace. A
re-jigging may be in order?

 

[Nicholas Paldino [.NET/C# MVP]]

Personally, I like to keep them in separate projects. It's really a
subjective issue though. Sometimes, if you have a good number of
namespaces, but not a good number of classes in each, then one assembly
would be enough.

 

[Guest]

For an example like this, I would probably have them all in one project; if
there were more namespaces inside those namespaces, I would probably keep
them as separate projects. Personally, I prefer lots of smaller projects
rather than one big project.

But (and there' always a but), this is just personal preference. There are
advantages to both larger projects and smaller projects (larger projects are
usually easier to manage as you don't have t go searching for a component
that is missing; smaller projects are usually easier to pick up and use
elsewhere). However, the advantages of either are very small. Do whatever
feels right to you.