Oops, I knew I'm gonna miss something stupid :) Anyway, thanks Keith, I've added the interface part.
But, coming back to ndepend, it claims the list is for "direct" dependencies. But, I don't think going up the inheritance tree makes sense in terms of coupling. After all, we need direct dependencies, and if, for example my type inherits AccessViolationException, I actually shouldn't care about anything higher in the tree than AccessViolationException. What do you think? Thanks, Lev On Nov 30, 3:43 am, Keith <[EMAIL PROTECTED]> wrote: > You're definitely missing Interfaces on the given type (ISerializable, > _Exception). > > Also, it looks like NDepend is including *all* base types up to > Object, as well as CustomAttributes on their class definitions. This > means NDepend will always show a dependency on SerializableAttribute, > ClassInterfaceAttribute, and ComVisibleAttribute, since they appear on > System.Object's class definition. > > (Note: There's no need to include interfaces from base types since > they are included in the derived types.) > > On Nov 29, 10:36 am, Lev Danielyan <[EMAIL PROTECTED]> wrote: > > > Have I missed something, or NDepend is listing something that actually > > is not "directly" referenced by the give type. --~--~---------~--~----~------------~-------~--~----~ -- mono-cecil -~----------~----~----~----~------~----~------~--~---
