Basically, what I need is something like Dependecy Walker, but it should work with .NET applications. Is there anywhere such tool?
+2
A:
Dependency Walker will work with .Net too.
the .Net layer still needs to call down to the core Windows functions like LoadLibrary and GetProcAddress to do the actual work. It is at this core level that Dependency Walker understands what is going on. So, while Dependency Walker may not understand all the language specific complexities of your application, it will still be able to track all module activity at a core Windows API level.
Brian R. Bondy
2008-10-13 12:43:00
I think this is not correct. It will detect the dependencies to native assemblies, yes, but it will not detect/see dependencies to .NET assemblies. For example, it will show a dependency to, say, kernel32.dll, but it won't show dependencies to, say, System.ServiceModel.dll. Can you elaborate?
Christian.K
2008-10-15 09:01:29
+1
A:
During runtime Systernals' ProcessExplorer might be helpful to see an assemblys dependencies.
Also NDepend can show you the dependencies and how tightly your components are coupled.
tobsen
2008-10-13 19:37:39