Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How do I determine the dependencies of a .NET application? Does Dependency Walker work with managed apps? I’ve downloaded the latest and tried profiling the app, but it just exits without much of an explanation. If it doesn’t work with .NET, then is there some other tool that would help me debug a run-time DLL loading issue?
Dependency walker works on normal win32 binaries. All .NET dll’s and exe’s have a small stub header part which makes them look like normal binaries, but all it basically says is ‘load the CLR’ – so that’s all that dependency walker will tell you.
To see which things your .NET app actually relies on, you can use the tremendously excellent .NET reflector from Red Gate. (EDIT: Note that .NET Reflector is now a paid product. ILSpy is free and open source and very similar.)
Load your DLL into it, right click, and chose ‘Analyze’ – you’ll then see a ‘Depends On’ item which will show you all the other dll’s (and methods inside those dll’s) that it needs.
It can sometimes get trickier though, in that your app depends on X dll, and X dll is present, but for whatever reason can’t be loaded or located at runtime.
To troubleshoot those kinds of issues, Microsoft have an Assembly Binding Log Viewer which can show you what’s going on at runtime