I am packaging and deploying custom activex controls for use in IE5.
In order to make sure that the vb6 runtimes are available on the user's
machine, I built a dummy activex control and, in the package & deployment
wizard, removed everything but the vb6 runtime and OLE reference. I then
refer to this CAB from other real activex controls (in the wizard) as the
source for the runtime files. This results in a component download error --
the error log references an exe file called VB6run.exe, which is not the
name of the vb6 runtime dll, apparently. Can anyone direct me here -- what
is going on and what is the right method to package the runtimes? What is
VB6Run.exe, a self-extracting archive?