![]() Launch the setup.EXE and watch the %TEMP% folder. Setup.exe /s /x /b"C:\FolderInWhichMSIWillBeExtracted" /v"/qn" Here are 3 methods to extract the MSI file from an EXE. Sometimes the setup.exe is called something else. You can try to extract the MSI (and maybe other files). What if the MSI is buried inside an EXE? Solution1: EXTRACTION! If it totally blows up then maybe it’s an old InstallShield Setup.EXE What if the Setup.exe is in the same folder as the MSI? Do I NEED to use it?ĩ0% of the time, NO. $AppMSIName = 'Filename.MSI' # actual name of the MSI in the \Files folder This way I can these variables in either Install or Uninstall phases. I usually place the following code before the $installPhase = 'Pre-Installation' line so I only need to do it once. I’ll try to update it as I can.įuture articles will talk about non-MSI packages and how to make them work in PSADT. ![]() Much of this is somewhat covered in the PSADT manual but techniques and logging is out of scope for the PSADT manual. This is the first of my Packager-Specific Tips
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |