Hi David, This in not related to the installation package running with simple UI or not. This behavior is caused by the fact that Windows Installer cannot overwrite an application that is running. So, if your package is installing an application over the previous version, and the older one is still ...
Hi, I am afraid that you cannot prevent the user from modifying the INI after installation. That is not a problem since the user might want to modify the INI file. This could be, for example, if he or she desires for the application not to use a bundled JRE but rather another JRE installed on that m...
Hi, I am afraid that Windows Installer does not support .NET DLLs and neither does Advanced Installer. Only native Windows DLLs are supported. You could use some utility that converts .NET code to binary Windows native code. Such a utility, called ngen.exe, comes with the .NET framework. After this ...
Hi Eric, 1. Yes, I am afraid that the new product code generated is preventing the patching process from working properly. 2. I would need more details in order to see what is the cause for the error. Did you generated a new MSI starting from the latest version or from the older one. Please detail t...
Hi Leonard, You should use an Installed type of custom action. You can specify the command line for the executable. For more information on this please visit: http://www.advancedinstaller.com/user-guide/custom-action-types.html#installed-action Be careful to schedule this custom action after the fil...
Hi Larry, I'm afraid that you cannot pass a wild card as a file name in Advanced Installer. You cannot specify multiple identifiers using this method. This is the way Windows Installer works. To achieve what you want you have two possibilities: - place all your files in a folder and use the custom a...
Hi, Yes, that is right. You can only disable this functionality in the Control Panel. If the user manually launches the MSI file he is still able to modify it. Windows Installer does not overwrite a file that has a newer modify date. Whether a file will be over-written or not depends on the file ver...
Hi, In order for the folder name to be known when you try to remove the file, you should schedule the Property Set with Formatted before the RemoveFiles standard action. For example you could place it on InstallInitialize. Also, instead of a Property Set with Formatted you could try to use a Directo...
Hi, The AI generated MSI might not work correctly if the Windows Installer on that machine has a version less than 2.0. For more information on this please visit: http://www.advancedinstaller.com/requirements.html I assume you have upgraded to a newer version of Advanced Installer. Did the problem a...
Hi Mos, Simply including the EXE in the package will result in the files being copied on the target machines, but they will not be executed. To have them install, the MSI should launch them too. For this you should use an installed/attached custom action that will launch those files with the necessa...
This option cannot be set when building the package. However, when you install it, the user can change the download location in the second screen, if he/she wishes to do so.
By default the download location will be the folder where the MSI is located.