5/24/2023 0 Comments Wavepad old versionPrerequisites are NOT packaged with each build because they are enormous and redundant from build to build. When it comes time to create a CD for customers, I unpack the internal build that was tested and throw away the preinstall and autoinstall. The AutoInstall.exe takes it a step further and does a silent uninstall/install for automated testing jobs. A tremendous convenience for our internal testing. So it is the preinstall that invokes the bootstrapper after the old build is uninstalled. ![]() So, instead, it tells the user it is going to uninstall the old build and install the new one. If it is found, then the preinstall script knows to NOT execute the MyProduct.exe because it will just give the user the popup message you indicate. The preinstall.exe checks the ProductCode in the msi file and then sees if that ProductCode is in the registry (Windows Installer automation object). ![]() But it has the ability to not only specify the file to execute on unpack, but also allow command line option to select another file. The self-extracting package is created by PackageForTheWeb - an ancient free tool from the days I used InstallShield. I package the installer, consisting of bootstrapper, ini and msi/cab files, along with a preinstall.exe (AutoIt3 compiled script) in a self-extracting executable file. ![]() I found what I think is a better solution for our environment.
0 Comments
Leave a Reply. |