Interactive Install: If you want to install with some user interaction you can locate the property controlling the accept status of the license agreement and set that to the appropriate value - usually 1 - to indicate accepted license.ĭTF: Now the code answer. Setup.exe: You can also make a WiX Burn bundle (see link for code mockup) or use some sort of other tool to make a setup.exe that will install your original application and then other components in sequence - so there is nothing to trigger to install from the application. This command must be run from an elevated command prompt (admin rights): msiexec.exe /I "Installer.msi" /QN /L* "C:\msilog.log" ALLUSERS=1 MSI logging information (short version: open log and search for "value 3" to find errors). Some digressions and suggestions first: MSI can be installed via msiexec.exe commands, Powershell, DTF C# (see below), WMI, MSI API ( COM, Win32).īatch: With that said, why don't you just install using a regular batch file? The /QN switch will bypass the entire setup GUI-sequence and then there should be no need to accept any license agreements. I would assume you would also need to run elevated - with admin rights - to kick off your installs (per-machine installations). It can work, but it may trigger serious problems with anti-virus and malware scanners. Caution: I would avoid triggering software installation from within an application binary - unless you are making an actual setup launcher application.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
June 2023
Categories |