burn

Burn (WiX bootstrapper) does not uninstall MSI package

折月煮酒 提交于 2019-12-22 09:39:24
问题 I have a Burn bundle with this chain: <Chain> <PackageGroupRef Id="NetFx40Web"/> <MsiPackage SourceFile="c:\\My\\Path\\MyMsi.msi" Id="MyMsi" DisplayName="MyMsi" DisplayInternalUI="yes" Vital="yes"> <MsiProperty Name="INSTALLLOCATION" Value="[InstallFolder]" /> </MsiPackage> </Chain> Both .NET framework and my MSI files are installed correctly. But the MSI package is not uninstalled during uninstall procedure (both after clicking on the bootstrapper EXE or from Programs And Features). Is there

WIX Burn Bootstrapper not asking for admin rights for my MSI

ε祈祈猫儿з 提交于 2019-12-22 02:41:13
问题 I created an MSI with WIX that needs elevated permissions to work correctly. In the MSI Project, I specified this via <Package [...] InstallPrivileges="elevated" /> Now I included this MSI in a custom bootsrapper project, based on WixWPF Bootstrapper. As I understand it, the bootstrapper itself should not alter the machine state and thus should not require elevated privileges. I would now expect the Bootstrapper to automatically launch the integrated MSI with elevated priviliges, prompting

WIX Burn Bootstrapper not asking for admin rights for my MSI

流过昼夜 提交于 2019-12-22 02:41:03
问题 I created an MSI with WIX that needs elevated permissions to work correctly. In the MSI Project, I specified this via <Package [...] InstallPrivileges="elevated" /> Now I included this MSI in a custom bootsrapper project, based on WixWPF Bootstrapper. As I understand it, the bootstrapper itself should not alter the machine state and thus should not require elevated privileges. I would now expect the Bootstrapper to automatically launch the integrated MSI with elevated priviliges, prompting

Cancel Installation and Rollback using wix burn Bootstrapper UI

十年热恋 提交于 2019-12-21 21:35:00
问题 I am using Wix 3.7. I am trying to create wix burn bootstrapper that install my msi. I have added two buttons in my BA UI for Install and Cancel. i am using C# for BA UI design. I have added the follwoing code in Install button for launch installation. MySampleBA.Model.Engine.Detect(); MySampleBA.hwnd = IntPtr.Zero; MySampleBA.Model.Bootstrapper.PlanBegin += this.PlanBegin; MySampleBA.Model.Bootstrapper.DetectPackageComplete += this.DetectedPackage; MySampleBA.Model.Bootstrapper

Start application after installation using WiX/Burn

别说谁变了你拦得住时间么 提交于 2019-12-21 03:19:16
问题 I'm aware of similar questions in WiX MSI, but I'm having issues starting an application within a bootstrapper EXE file created with Burn after the installation. My full bundle is below. If it makes any difference to the scenario, the bootstrapper is started in passive mode, so the user shouldn't need to press anything. <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:bal="http://schemas.microsoft.com/wix/BalExtension" xmlns:util="http:/

Wix Installation - Using Burn to have Managed UI & Displaying Same Progress Text as Built In dialogs

扶醉桌前 提交于 2019-12-20 10:54:12
问题 I am using Wix Burn to install per-requisites of our project, I have used ManagedBootstrapperApplicationHost to have custom UI, I have been following project available from Wix Source code to create my Managed WPF application.. Now the problem is the Progress (Message) it shows that doesn't match the progress message we have using inbuilt UI - WixStandardBootstrapperApplication.RtfLicense Basically I am using following code from the Wix source private void ExecuteMsiMessage(object sender,

Wix installer bundle produces corrupt “msi”

匆匆过客 提交于 2019-12-20 05:29:10
问题 Using very simple code almost same as in examples: <?xml version="1.0" encoding="utf-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"> <Bundle Version="1.0" Manufacturer="ACME" UpgradeCode="6AF8AF7D-3B44-4496-9E64-56206DF66C55"> <BootstrapperApplicationRef Id="WixStandardBootstrapperApplication.RtfLicense"/> <Chain> <MsiPackage SourceFile="wpftoolkit.msi"/> </Chain> </Bundle> </Wix> I get a setup.msi file that produced error imidiatly in start: msiexec /i setup.msi /l*v log.txt log

Wix Managed Bootstrapper: Installing Net framework and adding entry in add-remove program even if we cancel product installation

可紊 提交于 2019-12-18 08:57:43
问题 In my managed bootstrapper, I'm packing Net framework 4.5.1 and VC Redistributable as follows: <PackageGroupRef Id = "NetFx451Redist" /> <PackageGroupRef Id = "VC_ReDist_120" After="NetFx451Redist" /> <RollbackBoundary /> <MsiPackage Id = "MainProduct" DisplayName = "$(var.ProductName)" DisplayInternalUI = "no" Visible = "no" Compressed = "yes" SourceFile = "$(var.MainProduct)" Vital = "yes" After = "NetFx451Redist" > On Windows 7 x64, where Net FW 4.5.1 is not present, by installing, this

Comprehensive list of command line flags/options for Burn/bootstrapper in WiX

给你一囗甜甜゛ 提交于 2019-12-18 05:06:07
问题 The title says it all. I can't seem to find a comprehensive list of commands/flags/things-I-can-do-from-the-command-line. 回答1: WiX installers will take the standard Windows Installer commandline switches, as documented here: https://msdn.microsoft.com/en-us/library/windows/desktop/aa367988(v=vs.85).aspx Any additional parameters that are added to the commandline will be passed on to your installer if you're using a custom burn installer. This was confirmed by the primary WiX maintainer on the

How do I reference the Reboot Pending Property in Burn (WiX)

China☆狼群 提交于 2019-12-18 05:01:31
问题 How do I reference the RebootPending property in a Burn (WiX) bootstrapper? I know the property name is RebootPending, which is actually referencing the MsiSystemRebootPending property in Windows Installer. I'm currently trying something like this: <bal:Condition Message="There is a restart pending. Please restart your computer before attempting to install !(loc.ProductName).">RebootPending = 0</bal:Condition> But it's always true, even when Windows Update has just finished an update and