Hi, my name is Ross Youngblood. I’ve toyed with the idea of a blog from time to time. This effort was the result of simply trying to comment on someone elses web post. I figured I might as well join the party and start a blog of my very own. (Wow! Gee whiz, really?, Gee thats sooooo Original!).
Today’s post is Windows related. In my work I’m migrating code from VS6.0 to VS2013 (VisualStudio 6 C++ compiler to Visual Studio 2013 C++ compiler).
Today I’m digging into the Dependency Walker. This is a product developed by an individual that was so great, Microsoft bought the company… then promptly stopped updating the product because there was no money in it apparently. See the Wikipedia page as well.
I finally decided to do a write up on using Dependency walker and dig into why it always seems to find DLL’s that cannot be resolved. This was well explained by Ofek’s Visual C++ Stuff site. If you want to know why I started this blog, it’s Ofek’s fault. Thanks Ofek!
So basically there will always be missing DLL’s from the Dependency Walker report:
The API-MS-WIN missing DLL highlighted is an API-SET which is discussed in Ofek’s site.
IESHIMS.DLL A Stack Overflow Post provided Microsoft Link which reportedly contains this DLL, but it looks like it’s another “delay loaded” dll which isn’t important.
The WLANAPI.DLL I didn’t find a specific explanation for why this one was missing.
It appears to be part of the Wireless LAN service. Could be the program was built on a machine WITH wireless LAN, and deployed on a machine without… but I know the program runs fine without this DLL. Strange. Still Digging.
Thats it for now. I’ve got to get back to work.
rossyoungbloodblog 