mfc ActiveX control install issue
-
Not sure if this belongs here or in the COM discussion. Since I created an mfc ActiveX control with the mfc ActiveX Wizard, I'll try here... I created my first ActiveX control, and successfully installed it on my machine with regsvr32 "my controls name" Then I fired up VB and verified that I could use the control in a VB application. I was fat dumb and happy. To test it, I sent the .ocx file to a friend and had him put it in C:\temp. (The controls name is transponder.ocx) I had him execute the following from "Start" "Run"... regsvr32 C:\temp\transponder.ocx When he executed the command, he got the following error... Load Library “C:\temp\transponder.ocx” failed – the specified module could not be found. Any idea what this is trying to tell me? I set up the project as a static build, so I don't think it's looking for any dlls.
-
Not sure if this belongs here or in the COM discussion. Since I created an mfc ActiveX control with the mfc ActiveX Wizard, I'll try here... I created my first ActiveX control, and successfully installed it on my machine with regsvr32 "my controls name" Then I fired up VB and verified that I could use the control in a VB application. I was fat dumb and happy. To test it, I sent the .ocx file to a friend and had him put it in C:\temp. (The controls name is transponder.ocx) I had him execute the following from "Start" "Run"... regsvr32 C:\temp\transponder.ocx When he executed the command, he got the following error... Load Library “C:\temp\transponder.ocx” failed – the specified module could not be found. Any idea what this is trying to tell me? I set up the project as a static build, so I don't think it's looking for any dlls.
Use dependancy walker to see what DLLs it does need. Even if it is statically linked to MFC, it may still require the C-runtime DLLs (e.g. msvcrt.dll). Dave
-
Use dependancy walker to see what DLLs it does need. Even if it is statically linked to MFC, it may still require the C-runtime DLLs (e.g. msvcrt.dll). Dave
WOW... According to dependency walker, it requires the following... kernel32.dll, user32.dll, gdi32.dll, comdlg32.dll, winspool.drv, advapi32.dll, shell32.dll, comctl32.dll, ole32.dll, olepro32.dll, oleaut32.dll at the first level Then each of them has a list! Is it necessary to include all these in an install utility? Does one of these look like a good candidate for something that's not typically loaded in a Win2000 installation? Thanks!