Hello!
I've written a signal processing software and i want to bundle it with the needed dlls now. So i used dependency walker. But the process monitor( sysinternals ) that i downloaded recently shows more dependencies obviously.Why!
For example the process monitor shows oleaccrc.dll and dependency walker only shows oleacc.dll. Or the process monitor shows AudioEng.dll and dependency walker doesn't. What shall i do now?
Have you read their faq? It's possible that oleacc.dll is dependent on oleaccrc.dll.
I've already found the error: I didn't start profiling. That is neccessary for dynamic dependencies.
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.
Microsoft: "You've got questions. We've got dancing paperclips
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks