I have a software that is written in VB6 and the setup is also the generic vb6 setup.exe, which is prepared by the Package and Deployment Wizard in the VB6 IDE.

My task is to convert the vb based setup into an msi. What i can see while installing the application using the generic setup is that it copies some files in the %ProgramFiles% where as some DLLs and OCXs in the C:\Windows\System32 folder.

My question is that if i identify the files and their locations, and make an MSI that does the same task, will it work? I can do the same copy file task using the MSI that the setup.exe is doing. I can also register the DLLs using the MSI.

Is it the right approach to it? kindly let me know.

thanks in advance,

with best regards,
Tushar Singh
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


I usually capture the VB6 setup and strip out the related info from the package.
If I recall correct the setup file will have a setup related file that points out which files to install, which one that will be registered (such as .OCX) and registry to write.

To ensure that you don't miss something I would capture the installation and just clean it up.
Answered 12/05/2006 by: AngelD
Red Belt

Please log in to comment
thanks angel. I am doing the same :) i though there is a better approach to it. If we have the VB project file, then we can directly make an MSI using that project file. However, for that one needs the project file and the source code.
Hence, i took a capture and created the install.

Thanks for your help.

Wish Best Regards,
Tushar Singh
Answered 12/07/2006 by: matrixtushar
Purple Belt

Please log in to comment