One or many business object dlls

I have read some posts that having one dll as opposed to many is better for performance, but the difference is negligible. However, I have a project that will have around 100 objects.

My question is - should I put all the objects in one dll (seperate logically with namespaces) or have seperate dlls. I have many interdependencies between objects and having multiple dlls would be bad because if I update on dll, then I need to update the reference to it in all other dlls that use it. I would also have circular references. The bad thing about having 1 dll is that multiple developers may have a hard time working on the dll at the same time.

Any opinions?

Quote:

---

The bad thing about having 1 dll is that multiple developers may have a hard time working on the dll at the same time.

---

If you are using VSS, then you shouldn't have any problems with that. You just have to have each developer working with a different object at a time.

I think the primary reason for having seperate dlls is when there is a clear distinction between different parts and those parts may work indendently of each other. For instance a set of objects meant for web use and others strictly meant for windows use. Then it makes sense to seperate since most often you will not be using them together or at least. Other than that type of situation I find it easier to maintain and deploy a single dll. Especially where you have interdependencies, unless of course you want to intentionally seperate out a set of base components from the implementation.

That is what I will most likely do. 1 dll, and 1 or more dlls for the base (abstract classes) where applicable.

Thanks for the opinions!

One side note is that VisualSourceSafe requires you to check out the project when you are adding a new class, so that will be an issue when mulitple developers need to do this. But this is still better than all the reference problems if using more than 1 dll.

Yes, but you only need the project checked out for a couple seconds to add a file. Then you check it back in. Tell all the developers to get the latest version every now and then, and also to check in the changes often. This will keep everything working up to speed.