3 ms·
I never understood why those responsible for Windows SDK dropped Dependency Walker, instead of updating to the new Windows ways of dynamic libraries. Most cert
by pjmlp 2y ago
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.
- emmanueloga_ 2y agoI suspect there were no career improvement opportunities behind the effort, simple as that.
- forrestthewoods 2y ago> instead of updating to the new Windows ways of dynamic libraries. What does this mean?
- pjmlp 2y agoAPI 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.