I ran into a couple of problems when trying to sign SHDOCVW.DLL
After I run tlbimp.exe on the above mentioned dll I get a signed
MyInterop.SCHDOCVW.DLL, BUT it is quite different from the
AxInterop.SHDocVw.dll generated by the Visual Studio when you add a reference
to the same dll above.
More specifically, the class names are different, and some of the event
argument classes are missing
(AxSHDocVw.DWebBrowserEvents2_DocumentCompleteEvent - this is an Event Arg
class actually).
It seems as if Visual Studio when asked to generate a reference to
SHDOCVW.DLL actually generates a reference to some other DLL. If anyone could
shed some light on this, I would highly appriciate it. Thank you.
Serg - 29 Nov 2004 03:03 GMT
Ok I got it. Needed to be using AxImp.exe. Sorry.
> I ran into a couple of problems when trying to sign SHDOCVW.DLL
>
[quoted text clipped - 11 lines]
> SHDOCVW.DLL actually generates a reference to some other DLL. If anyone could
> shed some light on this, I would highly appriciate it. Thank you.