Well, I kind of gave in to the hexdump/pattern match method.
After quite a few hours of hell on earth, I mean, struggling with Visual C++ basics, I figured out how to get the CLSID from a DLL with the above recommended libraries, only to realize that I would be able to run this code from a Windows machine only, due to its dependencies.
After carefully scavenging the DLLs with different hex dumpers and disassemblers, I found what it seems to be a reliable pattern to get the CLSID next to its entry point. Maybe not the ideal solution, but the best I could come up with, without messing (too much) with Windows.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.