wix

问题 How do I avoid distributing sensitive information in my WiX / MSI by accident? I distributed a password, machine name or login credentials by accident with my MSI file. How do I best deal with this problem? After deployment my application connects erronously to my QA / UAT systems instead of my production systems - because of a faulty debugging construct in my setup's custom action code. How can I detect and avoid this? How do I avoid distribution such information in general? This is a Q/A

问题 I have a installer which is working fine. I want to run custom action only in install and modify only. Here is my custom action: <Custom Action="UpdateAPMDBAPasswordAndStoreInRegistry" After="InstallFinalize"><![CDATA[&BaseModel = 3 OR &FeaturePostMaster = 3]]></Custom> The above custom action is not running when modify the the installer. It runs only when install the installer. After googled, i did this but it is also not working: <Custom Action="UpdateAPMDBAPasswordAndStoreInRegistry" After

问题 We use wix to create our setups. For upgrading, we use major upgrades as demonstrated in this answer by Rob Mensching. (In newer wix versions you can use the MajorUpgrade element.) This normally works well. The old product is removed, then the new product is installed. However, apparently the above is not completely equivalent to manually uninstalling the old product and then manually installing the new product. Consider for example the following scenario: version 1.0 of our product is

问题 How can I have my Wix package to download the required .NET Framework when it's not yet installed in the client's machine? I already have the condition to check for the installed .NET version but I'm not sure how to have it downloaded and installed when not found. ClickOnce does this automatically by checking the pre-requisites in the properties pages. I just need to have it done in Wix due to some other requirements. Thanks! 回答1: UPDATE Aug 2017: This very nice answer now appears outdated.

问题 I'm trying to create a custom action with "Value" attribute, I want to pass parameters to the C# code (the TARGETDIR and the version). However, I get an error stating that DLLENtry and Value cannot coexist. But the custom action without dllentry is invalid. This is the code: <CustomAction Id="SetMAWPrefferences" Value="InstallDir=[TARGETDIR];Version=2.0.0.1" Return="check" Execute="commit" BinaryKey="ImportExportBinary" /> And for it I get this error: Error 9 ICE68: Invalid custom action type

问题 I'm trying to create a custom action with "Value" attribute, I want to pass parameters to the C# code (the TARGETDIR and the version). However, I get an error stating that DLLENtry and Value cannot coexist. But the custom action without dllentry is invalid. This is the code: <CustomAction Id="SetMAWPrefferences" Value="InstallDir=[TARGETDIR];Version=2.0.0.1" Return="check" Execute="commit" BinaryKey="ImportExportBinary" /> And for it I get this error: Error 9 ICE68: Invalid custom action type

问题 Windows Installer self-repair can cause problems for both developers , system administrators and end users . Finding the solution can be difficult if you have limited MSI experience. This is a Q&A-style answer intended as a check list for solving self-repair problems . Here are a few common problem scenarios: Repeated Windows Installer self-repair might occur whenever you launch an application on your workstation. How can this be fixed, or how can components be disabled so it never occurs

问题 I want to Locate path of MSI from WIX Source code when we perform installation. I tried using $(sys.SOURCEFILEPATH) which returns what I need (C:\temp\myProj\sample.msi)). But when I copy MSI file to a different folder (D:\temp\sample.msi) and tried to install I am getting the same path as previous(C:\temp\myproj\sample.msi). Thanks for your answers in advance 回答1: The Windows Installer sets the OriginalDatabase property to the path of the installation database used to launch the installation

问题 I've experimented with deferred custom action type 18. I've read a lot of material on the internet including this similar question How to add a WiX custom action that happens only on uninstall (via MSI)? which gives a big truth table of properties, but nothing seems to match my experiences with my Wix. I've upgraded to the latest Wix 3.11. File element is within the directory structure... <File Id='ReplaceRegistryEntriesFile' Source='MikeyRegistryReset.bat' DiskId='1' /> The rest is under

问题 I'm trying to do a WiX installer with a service install for my C# project. It's the first time I try and I don't understand why it doesn't work. I have set a ServiceInstall but when I run the setup, I'm blocked in this page : After a few seconds I got the error : I created the WiX install from a Visual Studio Installer with the same parameters. There is the code : <Product ... /> <Feature Id="ProductFeature" Title="$(var.product)" Level="1"> <ComponentRef Id ="MyService"/> </Feature> <UIRef