I didn't interpret the post as needed framework assemblies, but rather as assemblies written for the application. Not everything can or should be loosely nor tightly coupled. But when I see a chain of assemblies, I look to see if there should be some loose 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 ---