Side note: The command line "C:\Setup.exe /x // /l*v install.log" (from an example on that page) yields the same message: "Invalid command line". file.html which lists (among others) the command line switches "/newinst " and "/upgrdinst " which go into the right direction (uninstall missing) but I don't see how to get or. I'm trying not to put too much into this conversation. I imagine to control this behaviour by command line options, like "/install", "/upgrade", "/repair" (not relevant in this scenario) and "/remove". This is obviously not the same in a silent scenario. When I interactively start the installer, it runs either an install or an upgrade operation, depending on whether or not an older version is already installed if the same version is installed, I have the choice of modify, repair or remove operations. After successfully installing or updating, I start a test suite for the application. By checking before and after running the installer, I can verify that the correct operation occurred. I know how to check whether the product is already installed on a machine, and which version of it, by querying the registry. The relevant scenario for the automated test is "unattended install" with the "/qn" switch so that no dialogs pop up. The installer is a single exe file which, when run interactively, should start with a language selection dialog. I am planning to create automated tests for the installer. To give you a full picture of what I want to achieve: Sorry but I am not using the "multiple instance" feature. There is some contradictory(seemingly, at least) information available like the "/upgrdinst" and "/upgrade" switches, but when I use any of them (like "MyInstaller.exe /update"), I get the message "Invalid command line". I tried finding hints for command line switches that force a fresh or update install, or an uninstall operation. If a younger version is installed, upgrade and fresh install should fail, but uninstall should succeed.If an older version is installed, upgrade and uninstall should succeed, but fresh install should fail.If the product isn't installed yet, an upgrade install should fail, and so should uninstall, but fresh install should succeed.I expect the following outcomes of my test: I am aware that the installer must run elevated. I will use the "/qn" (no UI) and the "/L*V" (verbose logging) switches. I want to test new install, upgrade install, and uninstall.
This requires launching the installer from the command line with no UI interaction. Now I want to create automated tests for the installer. It runs fine when I double click the resulting exe file. I created an installer (*.exe with everything inside one file) with AI 19.9.
0 kommentar(er)
