I'm afraid that performing the INI searches again at a later time is not possible. You can only implement your own custom action that performs the INI searches and schedule it at the point you need.
oops!, I would like to ask why but I guess I will not bother.
I thought that the update process first performed a uninstall and then a install, then my idea was that in the uninstall I could copy the files to my backup location and then the search in the install process would always find them.
What you are saying is that the search is performed at ...
I am having a show-stopper random problem with my advanced installer setup.
I am going to send you by email the aip file and wo detailed logs, one where everything works as expected and another where does not work well, I hope you can help me with this one.
The only way I have found to make the repair option work, has been by checking the "Do not delete extracted MSI and CAB files" option. The problem I have with that option is that when the program is uninstalled the extracted MSI and CAB files are never deleted.
Today I had time to check the second solution and it also works, I am going to follow your advice, but I am wondering why do you think that the latter is a better solution. I supose it has to do with not affecting other possible functionalities or cases.
The registry entry exist, I had checked all that before (see the image attached), in fact it is the same condition to check if the pre-requisite is installed in the full package build and in that works perfectly.
registry1.png
What I dont understand is where have you seen in the log I sent ...
If you look at the first image I posted, it is the properties of the exe generated by advanced installer and it has two version numbers: Product version (three digits) File version (four digits)
When I import that file to the advanced installer "updater configuration project", imports the 4 ...
I have sent in an email to support the files requested.
The email subject is "Re: Use a extended search in Launch Conditions does not work due to be executed too late"
I have created an updates configuration project and when I create new updates after selecting the setup exe file which generates the update it is importing automatically the product version, but instead of importing the Product Version of the exe it is importing the File Version which has an ...
FOLLOW US
Get the latest news in Application Packaging