burn

问题 When installing my software I need to take care another msi package is uninstalled before. Is this possible? Can burn do this for me? 回答1: MSI / Major Upgrade : You can add entries to the Upgrade table in one or all of the MSI files you install. Then the older / other MSI will be uninstalled before (or after) your MSI is installed. This is MSI's built in "major upgrade" feature intended to deliver upgrades for your own products, but you can uninstall any product you want that is MSI-based -

问题 I have created a bundle using WIX. <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"> <Bundle Name="ClientSoft" Version="1.0.0.0" Manufacturer="Tests" UpgradeCode="GUID"> <BootstrapperApplicationRef Id="WixStandardBootstrapperApplication.RtfLicense" /> <Chain> <MsiPackage SourceFile="file1.msi" Visible="yes"/> <MsiPackage SourceFile="file2.msi" Visible="yes"/> </Chain> </Bundle> </Wix> I am installing only MSI files. The bundle will be executed with

问题 As in title, when I have some MSI package, is it possible to see which other packages depend on it? If yes, how? If that's not possible, is it at least possible to tell Msiexec to uninstall all depending packages as needed? 回答1: In short: yes and no. I guess . Several MSI files can be installed in sequence without there being any reliable way to tell if they are actually related as products, but they can also be bundled together by various mechanisms so they can install as a "single unit"

问题 It's been a while since I've done any WiX, but just found out that a bit of an existing bootstrapper exe I wrote ages ago, isn't actually doing what I thought it was - doh !! I've seen other people with similar issues, but I still can't figure out why it's not working. I'm basically trying to determine if a particular version of SQL SMO is installed and am looking in the registry at this location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SharedManagementObjects

问题 I have x64 and x86 versions of my installer .msi, and want to ship a single executable which simply checks the machine architecture and runs the x86/x64 MSI . The MSIs are basically identical, they install the same AnyCPU files, which I bundle in a shared .cab file so as not to double the size of the installer. So far I've tried WiX Burn, which pops up a GUI which I don't want (I just want to use the MSI GUI), and I tried disabling the burn GUI via /silent flag - this propagates this flag to

问题 I have x64 and x86 versions of my installer .msi, and want to ship a single executable which simply checks the machine architecture and runs the x86/x64 MSI . The MSIs are basically identical, they install the same AnyCPU files, which I bundle in a shared .cab file so as not to double the size of the installer. So far I've tried WiX Burn, which pops up a GUI which I don't want (I just want to use the MSI GUI), and I tried disabling the burn GUI via /silent flag - this propagates this flag to

问题 I have created a wix bootstrapper that runs fine on all computers when no theme file is used. If I use a theme file, it will run on my computer but not on anyone else's. <BootstrapperApplicationRef Id="WixStandardBootstrapperApplication.RtfLicense" > <bal:WixStandardBootstrapperApplication LicenseFile="C:\eula.rtf" ThemeFile="C:\myTheme.xml" /> </BootstrapperApplicationRef> 回答1: First, look at the bundle log file on the other machines to see the error. Likely the message will indicate there

问题 Looking through the source of the Wix Standard Bootstrapper application, it appears that each package has a DisplayName property: pPackage->sczDisplayName However, the BootstrapperCore dll that is used in the WiX Setup project does not have this property. Is there any way to extract this property from the bundles in managed code? 回答1: I ported the Bal code into C#, trying to make it work exactly like the C++ code: using System; using System.Collections.Generic; using System.IO; using System

问题 Looking through the source of the Wix Standard Bootstrapper application, it appears that each package has a DisplayName property: pPackage->sczDisplayName However, the BootstrapperCore dll that is used in the WiX Setup project does not have this property. Is there any way to extract this property from the bundles in managed code? 回答1: I ported the Bal code into C#, trying to make it work exactly like the C++ code: using System; using System.Collections.Generic; using System.IO; using System

问题 Here's my Fragment <Fragment> <Variable Name="Hasp_BundleVersion" Value="7.54.8889.1" /> <Variable Name="Hasp_IsInstalled" /> <Variable Name="Hasp_InstalledVersion" /> <util:RegistrySearch Id="Hasp_IsInstalled" Variable="Hasp_IsInstalled" Root="HKLM" Key="SOFTWARE\Aladdin Knowledge Systems\HASP\Driver\Installer" Value="Version" Result="exists" /> <util:RegistrySearch Condition="Hasp_IsInstalled" After="Hasp_IsInstalled" Variable="Hasp_InstalledVersion" Root="HKLM" Key="SOFTWARE\Aladdin