#Installbuilder delete installdir if installer fails how to#Would appreciate an indication of how to do this properly. I also tried the above with configuration/* instead of configuration in the remove entry. I figured maybe this would work if I first ' removed' the directory from the uninstaller, but the following also did nothing: This had no effect - perhaps because files in the directory were already on the uninstall list?Īlso no effect. And of course, that fails to delete the installation directory. I've tried all the options I could think of to delete these directories during uninstallation, but only a deleteFiles action in postUninstallerActionList seems to do the trick. For example, $/configuration is one such. The API MsiGetProductInfo (and equivalents) given the ProductCode and INSTALLPROPERTY_INSTALLLOCATION will return that main application folder location.My application's installation directory has a number of directories that accumulate additional files through normal use of the application. #Installbuilder delete installdir if installer fails install#This result in the install location being in the uninstall registry key, but that is basically an implementation detail. If INSTALLDIR is the location, just create a registry item (using the standard IDE) in the location of your choice and give it the value and this will resolve to the actual location when the item is written to the registry.Īnother useful tip is to have a type 51 custom action set ARPINSTALLLOCATION to the value and I'm not sure of thw InstallShield interface for that, but it requires no code. It will return the path to that component's install location, and it requires the file to be the key path of that component.įor future reference you can prepare for this in at least two ways. In InstallShield I think that's a system search. I have run the debug trace with the installer I created with 20.7.0. I get exactly the same message with the Enterprise version. When I tried to create the installer from my existing script, I immediately get the message I have uploaded, so I cant debug that one. #Installbuilder delete installdir if installer fails professional#Find a component guid for a file that was installed in that INSTALLDIR location (the main application folder, I assume) and use that. I downloaded InstallBuilder Professional 20.12.0 (Mac). #Installbuilder delete installdir if installer fails upgrade#Clearly the information is available somewhere, since ARP and the upgrade installer are able to successfully remove the application.Īlso, is there any way to access the values of SecureCustomProperties from the original installation during a major upgrade? I'm pretty sure I know the answer to that. Startup Failure Detection: VMware InstallBuilder installers will. Its not a friendly merge module, thats why its having this problem. It seems to me as though being able to find the installation location of the package you are upgrading should be a pretty basic feature since one would expect that when upgrading an application the user likely wants to put it back in the same place. Uninstall Functionality: An uninstall program is created as part of every installation. The Service Manager and dashboard run on the same machine and both have access to a local MySQL server installed as part of the MySQL Enterprise Monitor. It assumes that every client of the merge module understands a property called INSTALLDIR, and not all clients do, and yes, using INSTALLDIR is also an issue because thats primarily the name of a property thats exclusive to InstallShield. #Installbuilder delete installdir if installer fails code#I cannot find the upgrade code anywhere, either in that order or using the MS encoded/packed format. is the ProductCode of the installation I am upgrading. FindRelatedProducts shows: FindRelatedProducts: Found application: The uninstall is able to discover the INSTALLDIR from that installation and uninstall it. It doesn't know anything about the location of the original install. If they did, none of the code I created to back up and restore the user's settings (.Net config file entries) can be found because the Custom Action is looking in the default location. For example, if during the installation process your installer uncompresses a zip file, or if the user creates new files by hand, those files will not be removed. It's all working just fine as long as the user didn't choose to install it to a custom location. Only files bundled and unpacked directly by InstallBuilder in the installation step will be uninstalled. I am trying to build a major upgrade to our product using InstallShield.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |