burn

wix pass option to msi for repair

时间秒杀一切 提交于 2019-12-10 11:19:09
问题 When I repair using the msi, a registry entry is properly re-created. When using the exe generated by Burn, the entry is not-recreated, unless the exe associated with the reg entry also requires compare. I wonder if, when burn invokes msi, if it is overriding the default /fm behavior of msiexec. That switch means "repair all required computer-specific registry entries " Is there any way I can confirm, deny, or modify that behavior? 回答1: When planning a "Repair" operation in Burn the

Forcing WiX Burn bootstrapper to allow MSI files to use REINSTALLMODE=amus

给你一囗甜甜゛ 提交于 2019-12-10 10:55:57
问题 Since I wasn't a part of my company when our build process was designed and implemented (and has been successful for quite a few years now), I found out that there were things that were being done that may be looked at as 'hacks' to MSI 'purists'. However, in order to get a workable installer with Visual Studio 2012, I've been doing the best I can to mimic what was being done with the .vdproj files in Visual Studio 2010. Of the many snags I've hit, this one seems to be the last one that I can

Bootstrapper Application UI - How To move between pages

我怕爱的太早我们不能终老 提交于 2019-12-10 09:54:00
问题 I am writing a Bootstrapper Application and want to create the UI for it using the WixStandardBootstrapperApplication. I want the UI such that on the first page(Install page), I see the standard EULA and a checkbox which says I accept and a button to proceed on the next page (Options page) which should get enabled only after I select the checkbox. On the next page, I list some text and want to have another checkbox, which kind of again says I accept and a button to Install which gets enabled

WiX Burn - Determine what items are already installed

六月ゝ 毕业季﹏ 提交于 2019-12-09 05:36:36
问题 I've a burn installation whereby the user can select which of three options to install - each one directly relates to one of three MsiPackages in a chain, such as : <Chain> <MsiPackage SourceFile="..\ProductA\bin\Release\ProductA.msi" InstallCondition="chkProductA" /> <MsiPackage SourceFile="..\ProductB\bin\Release\ProductB.msi" InstallCondition="chkProductA" /> <MsiPackage SourceFile="..\ProductC\bin\Release\ProductC.msi" InstallCondition="chkProductC" /> </Chain> All fine. However, when I

Get feature installation cost prior to installation

泄露秘密 提交于 2019-12-08 18:11:24
We're making a custom boostrapper / external UI for our installation. We want to provide a "Custom Installation" dialog (like in MSI) to allow the user to choose feature(s) they want to install or remove. Currently, we are able to read the features (and other feature details like description) from the MSI database itself (by running an SQL query on the Feature table). However, we also want to display the cost of installing a feature. Windows Installer "Custom Installation" dialog is capable of doing this. I think we can mimic the behavior by doing the following: Pick a Feature that you want to

Wix Burn Bootstrapper MajorUpgrade

不想你离开。 提交于 2019-12-08 08:32:52
问题 I use Wix 3.7 to create bootstrapped installer with custom WPF UI. I want to implement the following use case: 1. User downloads installer for version 1 of the product and installs. 2. User downloads installer for version 2 and runs installer, which detects previous version and suggests upgrading. 3. User presses 'Upgrage' button and has the product upgraded to version 2. I get the problem with the 3rd step. On user action I do the following: _bootstrapper.Engine.Plan(LaunchAction

WiX Burn: LaunchTarget fails with error 0x80070002

二次信任 提交于 2019-12-08 06:15:25
问题 Setting LaunchTarget e.g. to "cmd.exe" works fine, after the installation of the burn package, the desired command line window pops up. However, setting LaunchTarget to for example "[InstallFolder]\Path\To\Postinstallexecutable.exe" yields an error: Error 0x80070002: Failed to launch target: C:\Program Files (x86)\Path\To\Postinstallexecutable.exe The path is correct, executing "C:\Program Files (x86)\Path\To\Postinstallexecutable.exe" at the command line works fine. Is this a bug or am I

WiX ManagedBootstrapper SetDownloadSource confusion

懵懂的女人 提交于 2019-12-08 04:32:08
问题 I am a bit confused by the method Engine.SetDownloadSource(). What I am trying to do is change the download URL for the bundled packages from an external website to an internal one. (If there is an easier way to do this, I am open to other suggestions). Now for the problem. When calling this method it is asking for a user and password. I am not sure where I should get this info from. string downloadSource = Path.Combine(WebSitePath(), "WebSetup/WebSetupData/", Path.GetFileName(args

Downgrade File in MajorUpgrade

大兔子大兔子 提交于 2019-12-08 03:31:12
问题 EDIT Please see the small repro at the bottom. I have the same issue as here: Windows installer deletes versioned file during product upgrade, instead of downgrading it File Table |File | Component_ | FileName | FileSize | Version| -----------|-------------------------------------------------------------------------------------------------------------------------------------------- old MSI |fileEcMWtDjRdBXxvVHY.WvW_XXJI4GZcq5iAszC_F3KIwk | Cj9pc73bMjDSVVGUqS81_nPSltSFuUEweshtzct2AHi4 |

Get feature installation cost prior to installation

流过昼夜 提交于 2019-12-08 03:19:04
问题 We're making a custom boostrapper / external UI for our installation. We want to provide a "Custom Installation" dialog (like in MSI) to allow the user to choose feature(s) they want to install or remove. Currently, we are able to read the features (and other feature details like description) from the MSI database itself (by running an SQL query on the Feature table). However, we also want to display the cost of installing a feature. Windows Installer "Custom Installation" dialog is capable