wix

问题 I need to check whether an any version of some product is already installed. <RegistrySearch Id="MyId" Root="HKLM" Key="SOFTWARE\Company\{ANY FOLDER}" Name="MY_KEY_NAME" Type="file" /> Is it possible to use RegistrySearch for searching in all subdirectories? 回答1: AppSearch / RegLocator doesn't support recursion. You'll either need a custom action or change the way you store data in the registry. 回答2: To my knowledge and from the documentation I see nothing that points to RegistrySearch

问题 I have three products which have their installers in .exe files. Let us say the installers for the three three products are Product_A.exe Product_B.exe Product_C.exe I want to create a msi file using wix toolset which will install these three exe installers. What is the best way to do this? I am new to these so please help. Any example would be highly appreciated I also plan to uninstall these products once I uninstall my msi. Thanks in advance for any help 回答1: Tools : There are a number of

问题 I have an application packaged with MSI that is made into a WiX bundle together with various required third-party tools. I have disabled modify and repair actions in the MSI du to how the application works, to require full uninstall before installing the same version again. When I run the MSI separately, it works as expected: the installer cannot be run twice. The same applies when running the exact same Bundle again. But simply by rebuilding the bundle (using same UpgradeCode and Version ),

问题 I have an application packaged with MSI that is made into a WiX bundle together with various required third-party tools. I have disabled modify and repair actions in the MSI du to how the application works, to require full uninstall before installing the same version again. When I run the MSI separately, it works as expected: the installer cannot be run twice. The same applies when running the exact same Bundle again. But simply by rebuilding the bundle (using same UpgradeCode and Version ),

问题 I am working on a Wix installer to support Windows 7 SP1, Windows 8 and higher. I can successfully verify Windows 7 with Service Pack 1, however my windows 8 launch condition continually fails. My stripped back condition for windows 8 is, <bal:Condition Message="Windows 8 or higher supported...."><![CDATA[Installed OR VersionNT >= 602]]></bal:Condition> Log Entry [0638:0D20][2015-08-28T07:47:17]i001: Burn v3.9.1208.0, Windows v6.3 (Build 9600: Service Pack 0) [0638:0D20][2015-08-28T07:47:18

问题 I am trying to setup a WiX installer that install a windows service and handles upgrades and updates. The installer works like a charm, the user installs the service under the LocalSystem account then a service engineer has to assign a domain account to that service. Here is my service installer component: <Component Id="my_exe_Component"> <File Id="Myexe" Source="$(var.Myproject.TargetPath)" KeyPath="yes" /> <ServiceInstall Id="my_exe" Type="ownProcess" Vital="no" Name="NME" DisplayName="My

问题 I can't find anywhere how to set parameters in the wix bootstrapper so that firewalls and anti-viruses do not treat it as a threat. My bootstrapper on other devices displays information that it is a threat. Or it doesn't start without any information. Edit: I create something like this: <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:fw="http://schemas.microsoft.com/wix/FirewallExtension"> <Bundle Name="Bootstrapper13" Version="1.0.0.0"

问题 I can't find anywhere how to set parameters in the wix bootstrapper so that firewalls and anti-viruses do not treat it as a threat. My bootstrapper on other devices displays information that it is a threat. Or it doesn't start without any information. Edit: I create something like this: <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:fw="http://schemas.microsoft.com/wix/FirewallExtension"> <Bundle Name="Bootstrapper13" Version="1.0.0.0"

问题 We have a problem that a fie is not installed upon a major update We have a major update with <MajorUpgrade Schedule="afterInstallInitialize"... We an old component with 1 file (xyz.exe Version 12.34) from a external manufacturer We have now a new file from a new manufacturer and with the same name (xyz.exe Version 2.34). The new file has a lower version number than the old one. We created a new component in the install package and removed the old component (in fact we gave it a new guid)

问题 I am creating a ASP.net core 2.0 WEB API project that is required to be deploy as a Windows service on a system using a MSI setup. Is there any way I can do it ? Things that I have already tried: I created an MSI using Setup Project but it doesn't load any dependencies. I tried to create an msi using WIX but it shows error The WiX Toolset v3.11 (or newer) build tools must be installed to build this project I have tried solution which are already answered on this and this. 回答1: Short on time,