This has a write up on how to find the name of a .dll that your .dll cannot seem to find itself when your .dll starts barfing up an opaque error like this. I haven't tried it myself. Dependency Walker might be a tool one may use for this challenge too. I'm not sure.
No comments:
Post a Comment