Has anyone created an MSI package for VB6 Pro? I just created one with AdminStudio 6.0 and got several (about 170) warnings about Undefined CLSID, Undefined typelib, Undefined ProgID, etc. It said that these warnings could cause ICE33 errors when the application was run. I used the snapshot method to create the MSI. The package created successfully and I was able to install it on a test machine. The application seems to run OK but the warnings have me worried. If anyone has a fix for this or another procedure for creating the MSI, I would appreciate any information you can pass along.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hi,

I think that u have not captured the HKCR keys properly.Install the source and check for vb keys and u will find those missing keys in your msi.
Answered 11/05/2004 by: stephen
Senior Yellow Belt

Please log in to comment
0
I find ICE errors annoying and in most cases useless to troubleshoot.

Your capture has placed the registry entries into components and not into the Installer tables as expected by the Validation Wizard.

You will find that even with the ICE errors your capture will work.....all of mine have.

If you are sure that you have captured it correctly then I wouldnt worry too much about the ICE errors.

I know that flys in the face of ICE standard.......but I'm yet to find an msi without some form of ICE error.
Answered 11/05/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity