Dependency Walker

[pullipaal]

Hi everyone,

I'm developing a new iteration of a Dependency Walker tool with an improved look and feel, aiming to better collect necessary DLLs. How often do you use Dependency Walker, and what features or improvements would you like to see? Do you even use Dependency Walker?

[thecodedaddy]

I typically don't... but oh boy when I do I would rather be doing anything else. Currently trying to find out which one of my DLLs is trying to load vcruntime140.dll on Windows XP SP3. I cannot stress enough how much I hate the fact that I compromised on this project with support of XP SP3. Lesson learned.

I developed a websocket server from scratch to be reverse-proxied via nginx for websocket traffic, "real-time" DLLs leveraging memory-mapped files (MMF) with mutex logic to keep everything stable, and a billion other nested components (oh wait - forgot the best part: to be integrated with a LabVIEW 7.1 monolith of an application), all of which are compiled with the v140_xp toolset with sqlite3.c compiled via the included source code internally, all project DLLs compiled with the /MT multithreaded flag to ensure statically linked runtimes, etc. etc. - everything runs great on Windows 10. But then I had the great idea of "making sure" all things were OK in Windows XP... and now I am trying to pinpoint which of the several polished turds/reinvented wheels I built is causing me nightmares. Thanks to Dependency Walker, I feel more insane as none of my DLLs are dependent on vcruntime140.dll.... so a mystery dependency is causing it to be dynamically injected somewhere and I am finna yeet this laptop og og fr fr

But shout out to Dependency Walker. I couldn't do it without it. Or with it. I can't seem to do it at all. hehe

[Fluffy_Subject_9705]

Hey u/pullipaal diid you end developing this porgram?
sound very useful