we have noticed a difference in the Automation IDs generated by MSI setups.
On desktop operating systems, the Automation IDs are set correctly. However, on Windows Server environments, the Automation IDs are either missing or differ from those on desktop systems ...
yes we want the "Maintenance Mode" with the new Build.
1) build a MSI 2) install the MSI 3) delete the MSI 4) build new msi with newer Version and ProductCode 5) start new MSI and get the "Maintenance Mode"
acually behaviour ist that MSI start a new Installation and not the "Maintenance Mode"
That is not the current behavior. No uninstallation is offered. A normal installation opens in our case: select language, destination, and then it is installed. Even if a setup installation has already been completed.
Thx for your reply. After we change that the ProductCode. The msi/exe try to install over the installed product. We also diabeld the setting "Allow side by side installs" and "Unintall old, version first". The changeing of the ProductCode didnt work as we expected.
wir haben ein Setup mit einer Größe von etwa 20 MB, das problemlos funktioniert. Nach dem Hinzufügen einer Custom Action, die eine stand-alone .NET DLL (ca. 20 KB groß) nutzt und keinerlei .NET Framework-Installation benötigt, ist die Setup-Datei auf ganze 600 MB angewachsen.
Thanks for your hints so far, but to make our problem as transparent as possible, we send you the following examples via Email to "support at advancedinstaller dot com" with the following prefix before the title "[Quenteux1603]".
The setup is to be executed at the customer's site via powershell. It is very important to our support that the ReturnCode that our exe returns can be seen in the powershell via LastErrorResult. If this is not possible with AdvancedInstaller or with the Windows Installer (msiexec), we unfortunately ...
During our evaluation of the advanced installer we encountered a problem. We have an exe that is called in a CustomAction. The return code of this exe should be the return code of the AdvancedInstaller to enable further error handling. Unfortunately, the return code is always set to 1603 after the ...
FOLLOW US
Get the latest news in Application Packaging