vortibrowser.blogg.se - Installbuilder installer filename

#Installbuilder installer filename how to
#Installbuilder installer filename .exe
#Installbuilder installer filename install

Please find below an example of what I mean here:

Hi you give us more information about your specific scenario? Depending on how many files you expect to update from one version to the next one you could use the update installer or a regular installer acting like an update installer.

#Installbuilder installer filename .exe

I would like to keep only the latest .exe installed on the common folder and clean up the older ones, even when installing a more dated product. which is not the case anymore here, if the names include version numbers. 'overwritePolicy.onlyIfNewer' assumes the destination file have the same name ("Activation.exe"). How would you face that situation in the individual installers? Notice the rest of the files of the individual installers use the default overwritePolicy.Always.īut now we need to include version number at the fileName level for the Activation file, e.g. Right now we use "overwritePolicy.onlyIfNewer" for that single file, so if costumer installs an old product, it keeps the Activation.exe up-to-date. We have N independent individual installers that we release on different dates.Īnd we have 1 single common file Activation.exe for all the N products, which comes with the individual installers, which after installing all the files of the product it just drop the file Activation.exe into the common folder. Thank you in advance for any help and paying attention to this problem,

#Installbuilder installer filename how to

Is this possible ? There is some example on how to achieve this using InstallBuilder ?

#Installbuilder installer filename install

If you install a newer product how to delete only Activation2019.exe and dropping Activation2020.exe ?.

2) There's an older Activation2019.exe already in the common installation folder.

If you install an older product how to avoid dropping an Activation2019.exe file ?.

1) There's a latest Activation2020.exe already in the common installation folder.

In this scenario, instead of overwriting a file we need to remove the older one and drop the new one. (For this purpose 'project.overwritePolicy' to "onlyIfNewer" just works OK)īut now the Activation executable needs to have a version number in its name. In my case, we make different installers for different products that goes inside a common folder, and there's a unique Activation executable for all the products.Įach installer drops the Activation executable to the common folder, and in case the installer is more dated it installs the product but doesn't overwrite the Activation executable. What happens if instead of overwriting it, the newer destination file changed its name ? e.g. I know we can set 'project.overwritePolicy' to "onlyIfNewer", to avoid overwriting a distribution file with a more dated version of it.īut that assumes that the destination file has the same name, but different timestamp. Hi there, I didn't find an answer to this question in the docs.