wix3

How can a silent installer be created in WiX that does not display any UI dialogs to the user and installs, upgrades and uninstalls with default settings? Just don't include any UI/UIRef elements and then no UI will be included :) Christopher Painter Windows Installer (MSI) uses the following command line arguments to be silent: Silent install or silent major upgrade: msiexec.exe /i foo.msi /qn Silent minor upgrade: msiexec.exe /i foo.msi REINSTALL=ALL REINSTALLMODE=vomus /qn Silent uninstall: msiexec.exe /x foo.msi /qn Executable path: C:\Windows\system32\msiexec.exe Installer .exe's created

I have a MSI build using WiX version 3. All previous installers for the product we are deploying worked fine with the configuration specified (that is: if previous version exists, remove, then install the new version) - however, the new MSIs we build don't install all files when it runs through the 'remove first' path. If we manually remove the existing installation and then run the new version all the files are installed - and when I examine the MSI file in Orca the files and features are shown and seem to be fine. We have tried running with verbose and extra logging turned on ( /l*vx )

This is the error that is thrown by our automated build suite on Windows 2008, while running ICEs (after migrating from WiX 2.0 to WiX 3.0): LGHT0217: Error executing ICE action 'ICE01'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wix.sourceforge.net/faq.html#Error217 for details and how to solve this problem. The following string format was not expected by the external UI message logger: "The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support

I am using 2 500K bitmaps in to display images on my WiX dialogs. They dramatically increase the size of the installation package, and what is worse - it looks there's no way to package them as a part of a .cab file since they're <binary> -es in the WiX terms. So, I thught, is there any way to use other file formats for bitmaps or WiX is tethered with BMP? Ideally it would be greate if there's a way to use .png format since it comes with a looseless compression option. The Windows Installer documentation for the Bitmap control states that the image should be a "bitmap" -- presumably a .BMP

I have to create an installation package using Wix. If an admin user is installing the package, it should install into %programfiles%/[applicationName], if the user is an non-admin user then it should install into its local profile folder( LocalAppDataFolder). How it is possible? I wrote this for ClickThrough a long time ago. Solution from that looks a lot like this (You provide a Property called "ApplicationFolderName"): <Property Id="A" Secure="yes" /> <DirectoryRef Id="TARGETDIR"> <Directory Id="ApplicationFolder" Name="App" /> </DirectoryRef> <Condition Message="Must specify TARGETDIR

I have a product that consists of multiple features that can be installed to different locations e.g. Feature 1 is an executable installed in Program Files and Feature 2 is a website installed in wwwroot. However both Feature 1 and Feature 2 rely on many of the same dll's and hence require the components containing those dll's to be installed in 2 different locations depending on which Features are installed. Is there a way to achieve this without defining every component twice? To provide a further complete example of what I am trying to achieve, the following complete wxs file can be