>Yes, I agree with that, but he has DLL1 requiring DLL2 requiring DLL3. Sounds like lots of tight coupling.

How so? Example:

Westwind.Utilities
Westwind.Web
Westwind.Web.Mvc

The last assembly depends on the previous two, the second on the first. It's a common scenario for modular design.

+++ Rick ---

>
>>Eh what? What John is describing sounds like a pretty common use case to me.
>>
>>Just about anything you add to a project has dependencies and if you're building even a reasonably complex piece of code breaking out code into logical assemblies is a good thing to promote reuse and isolation of concerns.
>>
>>+++ Rick ---