windows-installer

问题 Is there a possibility to retreive the MSI product code out of a MSI file without installing it with PowerShell? I want to compare the product code of a MSI file with the MSI codes installed on a maschine to find out if the file was installed in the past. 回答1: Here is a script that reads the product code based on this article: $path = "pathto.msi" $comObjWI = New-Object -ComObject WindowsInstaller.Installer $MSIDatabase = $comObjWI .GetType().InvokeMember("OpenDatabase","InvokeMethod",$Null,

问题 I install my application to a specific folder using the below wxs code: <Directory Id="TARGETDIR" Name="SourceDir"> <Directory Id="ProgramFilesFolder"> <Directory Id="INSTALLDIR" Name="CompanyName"> <Directory Id="SUBDIR" Name="Application Launcher"> <Component Id="ApplicationFiles" Guid="*"> <File Name="app.exe" Id="AppFile1" Source="app.exe" Vital="yes" /> </Component> </Directory> </Directory> </Directory> </Directory> I want to specify the installation folder with a parameter to be given

问题 Background information: We used to have a Visual Studio 2010 based installer project, but our install situation got a lot more complicated, and with the projects going away anyway in 2012, we figured we'd start learning WiX / InstallShield LE. The Problem: InstallShield LE seems far too limited in the MSI files it creates to fit our needs -- (example, if you check the Office 2007 prerequisite, even though the error says you need "Office 2007 or later" it will fail if you have Office 2010

问题 I am trying to register an out-of-process COM file (.exe) through WiX after extracting the COM registration from regspy.exe, and am running into the problem that the registry key I need to write is: <RegistryValue Value="C:\PROGRA~1\COMMON~1\file.exe /Automation" Type="String" /> Now I would like to use the Windows Installer property [CommonFilesFolder] as not everyone installs to C:\ For an in-process (.dll) the long name is acceptable: <RegistryValue Value="[CommonFilesFolder]file.dll" Type

问题 Now I use something like this: <Component Id="RegistryEntries" Guid="<guid>" KeyPath="yes"> <RegistryKey Root="HKCU" Key="<path>" Action="createAndRemoveOnUninstall"> <RegistryValue Name="myStrings" Action="append" Type="multiString"> 1 </RegistryValue> <RegistryValue Name="myStrings" Action="append" Type="multiString"> 2 </RegistryValue> <RegistryValue Name="myStrings" Action="append" Type="multiString"> 3 </RegistryValue> <RegistryValue Name="myString" Value="x" Type="string"/> <

问题 I installed an test application which has two features (FirstFeature & SecondFeature). I want to remove only one feature (SecondFeature) from the application. I tried using REMOVE property in command line. Here is the command used to remove SecondFeature. msiexec /x RemoveFeatures.msi REMOVE="SecondFeature" /L*V log.LOG But it is uninstalling the complete application. Log file shows that REMOVE=ALL is added by default. Here is the log file details. MSI (s) (24:B4) [17:39:05:231]: Command Line

问题 Currently I have an MSI which performs a major upgrade, and it is launched as: msiexec.exe /i installer.msi /qn REBOOT=ReallySuppress My question is regarding that particular property REBOOT=ReallySuppress : does this mean it will not restart the system but will do proper changes (if applied) when user reboot her system manually? Or will it simply ignore those things that require to restart the system? 回答1: The installer performs all the operations. The value ReallySuppress of REBOOT property

问题 I have built an MSI that I would like to deploy, and update frequently. Unfortunately, when you install the MSI, and then try to install a newer version of the same MSI, it fails with a message like "Another version of this product is already installed. Installation of this version cannot continue..." appears. The MSI was built with a Visual Studio 2008 Setup Project. I have tried setting the "Remove Previous Versions" property to both true and false, in an effort to just make newer versions

问题 Our product has an MSI installer (written in WiX) which basically copies some files into a folder c:\ourproduct and installs a windows service "ourwindowsservice". We'd like to add support for multiple instances of the service, and it should be possible to install/uninstall them independently of each other. Similar e.g. to SQL Server, each instance should have a name which can be passed to the MSI as a command line parameter. Example: instance "A" => copy files to "c:\ourproductA", install

问题 Following directory setting works perfectly for me. <Directory Id='TARGETDIR' Name='SourceDir'> <Directory Id="ProgramFilesFolder"> <Directory Id='INSTALLDIR' Name='MyApp'/> </Directory> </Directory> However, when I tried changing "ProgramFilesFolder" to " LocalAppDataFolder ", I got lots of error when using light to link and generate my msi: D:\runGroup.wxs(53) : error LGHT0204: ICE38: Component cmpA5561BE36D80EB58252E69DDA0C2FF8C installs to user profile. It must use a registry key under