Create a CAB file to install ActiveX for IE

I created a cab file containing my activex using CABARC.exe. I also created a .inf file. My inf file is as follows:

[version] signature="$CHICAGO$" AdvancedINF=2.0 [Add.Code] MySetup.exe=MySetup.exe [MySetup.exe] file-win32-x86=thiscab clsid={49892510-B520-4b35-8ADF-57084DD2F717} 

My html looks like this:

 <object name="secondobj" style='display:none' id='TestActivex' classid='CLSID:49892510-B520-4b35-8ADF-57084DD2F717' codebase='http://myurl/MySetup.cab#version=1,0,0,0'></object> 

I created CABARC using the following command:

 C:\tools\Cab\BIN>CABARC.EXE N MySetup.cab MySetup.msi setup.inf 

I also added http: // myurl to trusted sites. Now, when I first opened the html page in IE, I saw a yellow bar that I accepted. However, he never installed an activex control. I do not see the installation in my program files and I do not see anything in the event logs or in the temporary download folder or in the "add-on management". Now every time I open a webpage in IE, I no longer see the yellow panel.

Can anyone help me here?

+6
installation activex
source share
3 answers

It looks like my .inf is disabled. Here is what worked for me:

 [version] Signature="$CHICAGO$" AdvancedINF=2.0 [Setup Hooks] hook1=hook1 [hook1] run=msiexec.exe /i "%EXTRACT_DIR%\MySetup.msi" /qn 

To make a cab:

 CABARC.EXE N MyActiveX.cab MySetup.msi setup.inf 
+1
source share
  • It seems to me that you are installing the msi installer instead of the ActiveX control.
  • When you take your control from the MSI installer and pack it in a CAB, be sure to add its version to the INF file.

Hope this helps ...

Packaging ActiveX controls

+2
source share

VS 2008 provides an excellent CAB project. You can find it under Other Project Types / Installation and Deployment Project / CAB.

For simple CAB projects, you just need to add your component project.

If you also need to sign your CAB, you must edit the project properties by adding the post build signtool.exe command, but as soon as you can sign the component via the cmd line, you just need to copy the command line to publish the build event. Using the $ macro (ProjectDir) can help generalize the automatic build process.

+1
source share

All Articles