Debugging an activex CAB
Posted on 2003-02-24
I have a problematic ActiveX cab on my hands. The activex works and tests correctly when used in a VB application. However when using the object tag, pointing at a CAB file created with the packaging and deployment wizard, the activex will not initialize.
I'm pretty sure it has something a component not downloading and installing via IE. What lead s me to this conclusion is the following:
1) If I use an MSI created with Visual Studio Installer, and install the activex onto a computer and then access the same web page (cab), the borwser shows the correct components and the app works perfectly.
2) The OCX contains 5 controls, which are then aggreegated into another control, which is the control I cannot initialize. As a test, I took the htm file generated by the packaging and deployment wizard, which contains an object tag and clsid for all custom controls and classes in the ocx and viewed each object seperately. 4 of the 5 controls are visible in IE using the cab file on fresh (no msi) machine. This leads me to belive the the "final" control is not visible because of the problematic 5th control.
I'm not neccessarily looking for a solution to the problem. The info I seek is how do I go about debugging this situation? How can I tell what components are failing to Down load and install in this 5th control when run in IE. And possibly, why?
Thanks for your help guys.