Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I never understood why those responsible for Windows SDK dropped Dependency Walker, instead of updating to the new Windows ways of dynamic libraries.

Most certainly they keep having similar tooling in Redmond.



I suspect there were no career improvement opportunities behind the effort, simple as that.


> instead of updating to the new Windows ways of dynamic libraries.

What does this mean?


API Sets, SxS manifests, Visual C++ linker delay loading, .NET Assembly loading and related fusion cache, UWP sandbox loading, are some examples of changes the original dependency walker isn't capable to handle.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: