Removing that gets the following error in the MSI logs: DEBUG: Error 2819: Control Folder on dialog InstallDirDlg needs a property linked to it Basically this means that the “browse for folder” control isn’t linked up to an actual property value. You’ve used the value INSTALLLOCATION for the application folder – which in turn means … 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
If you open your .wixproj file in a text editor, you will see that your x64 configuration items are at the bottom of the file (below the import of the standard WiX build targets) and your x86 configuration is at the top (above the import). If you shift the XML for the x64 config so … 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
Save the license.rtf from WordPad. See this webpage (http://wixtoolset.org/documentation/manual/v3/wixui/wixui_customizations.html), specifically this section: There is a known issue with the rich text control used to display the text of the license file that can cause the text to appear blank until the user scrolls down in the control. This is typically caused by complex RTF content … Read more
Deferred custom actions can not directly access installer properties (reference). In fact, only CustomActionData property session.CustomActionData and other methods and properties listed here are available on the session object. Therefore, for a deferred custom action to retrieve a property such as the INSTALLLOCATION, you have to use a type 51 custom action — i.e. a … Read more
Keep variables in a separate wxi include file. Enables re-use, variables are faster to find and (if needed) allows for easier manipulation by an external tool. Define Platform variables for x86 and x64 builds <!– Product name as you want it to appear in Add/Remove Programs–> <?if $(var.Platform) = x64 ?> <?define ProductName = “Product … Read more