“Reference-Style” Answer: This is an alternative answer to the one below with several different options shown. Uninstalling an MSI file from the command line without using msiexec. The command you specify is correct: msiexec /x {A4BFF20C-A21E-4720-88E5-79D5A5AEB2E8} If you get “This action is only valid for products that are currently installed” you have used an unrecognized … Read more
Try to change the GUID of the components which are not uninstalling. I tried the same and it worked for me. It may be because the GUID is already registered in the registry by some other product. The cause is generally messed up component reference count in the registry – often it happens on dev-boxes … Read more
The log file provided shows that newer versions of a few files already on the machine: MSI (s) (0C:5C) [16:13:25:890]: Disallowing installation of component: {015A4DC1-56F4-562B-96B5-B3BE0D45FA5F} since the same component with higher versioned keyfile exists MSI (s) (0C:5C) [16:13:25:890]: Disallowing installation of component: {4B6A1404-3892-5BEF-AB47-8FE3149211A4} since the same component with higher versioned keyfile exists I’ve seen this … Read more
The file extension is a convenience, the content of the file is what really matters. The distinction makes it easier to manage the difference between the actual installation (wxs files) and the properties required to create the installation (wxi files). For example, your wxs files specify the product and its contents (which files you install) … Read more
You could update the OutputName of your .wixproj and use an MSBuild variable to pass through the version number or any other variable you like. My build script looks like this: set PRODUCTVERSION=7.1.0.1 MSBuild.exe /p:Configuration=Debug /p:ProductVersion=%PRODUCTVERSION% Installer.wixproj And my WiX project looks like this: <?xml version=”1.0″ encoding=”utf-8″?> <Project ToolsVersion=”4.0″ DefaultTargets=”Build” xmlns=”http://schemas.microsoft.com/developer/msbuild/2003″> <PropertyGroup> <Configuration Condition=” ‘$(Configuration)’ … Read more
Define the folder like this: <Directory Id=”TARGETDIR” Name=”SourceDir”> <Directory Id=”CommonAppDataFolder”> <Directory Id=”TestFolder” Name=”test”> <Directory Id=”ExampleFolder” Name=”example” /> </Directory> </Directory> </Directory> The important part here is the CommonAppDataFolder Id, which is known by Windows installer. You can find the full list of known system folders in the Windows Installer Property Reference. If you install any files … Read more
The accepted answer already mentions the ADDLOCAL property, but seems to imply that you can select only one feature. You can actually select multiple features by seperating them by commas like this: msiexec /i install.msi ADDLOCAL=Feature1,Feature2 or msiexec /i install.msi ADDLOCAL=Feature2,Feature3 Another hint: you can discover these feature names by opening the msi with orca. … Read more
I skipped it using: <UI> <UIRef Id=”WixUI_InstallDir” /> <Publish Dialog=”WelcomeDlg” Control=”Next” Event=”NewDialog” Value=”InstallDirDlg” Order=”2″>1</Publish> <Publish Dialog=”InstallDirDlg” Control=”Back” Event=”NewDialog” Value=”WelcomeDlg” Order=”2″>1</Publish> </UI>
The previous answer is out dated. WiX v4 is very close to being ready and I encourage active testing of it during the RC phase. In WiX v4, there is no installer for WiX. It’s a dotnet tool you install. If your a user of Votive, Votive is no more. Instead FireGiant has a closed … Read more
A non-advertised shortcut (Standard Shortcuts) is a standard windows shortcut. If you right-click it you will see the target field points to the executable that will be launched. If, for whatever reason, this executable is missing the application will simply fail. An advertised shortcut (Windows Installer Shortcuts) is a technology specific to Windows Installer. If … Read more