burn

WiX Burn: Reading LaunchTarget from Registry

你离开我真会死。 提交于 2019-12-05 20:33:46
I'm new with WiX, and I'm trying to have my Bootstrapper launch my installed application when it completes. To accomplish this, I'm using <Variable Name="LaunchTarget" Value="path_to_exe"/> However, it is not easy for me to get the path to the executable. The reason for this is because I'm using <Chain> to install some pre-requisites and then an msi that actually installs my exe. So to do this, the msi is writting the path to a known location in the registry, and then the bootstrapper reads it and uses it. The problem is that when the bootstrapper reads the registry, the msi hasn't run yet, so

Burn (WiX bootstrapper) does not uninstall MSI package

半世苍凉 提交于 2019-12-05 12:12:45
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 some way how to force uninstalling the MSI package? Burn will create a log file with detailed

WiX Burn 3.6 beta - custom UI examples

二次信任 提交于 2019-12-04 17:51:16
问题 Are there any good references/examples for WiX Burn 3.6 custom UI? I googled around, but they are broken pieces of the information. 回答1: The WiX installer itself is a good example and the source is freely available via CodePlex (WiX 3.6 Beta). Check out the WixUX project, which is the bootstrapper for the WiX 3.6 install. Another Stack Overflow question is Custom WIX Burn Bootstrapper user interface? , describing how to get started. Or if you get the latest weekly WiX releases, the project

Cancel Installation and Rollback using wix burn Bootstrapper UI

时光总嘲笑我的痴心妄想 提交于 2019-12-04 16:53:30
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.DetectComplete += this.DetectComplete; MySampleBA.Model.Bootstrapper.PlanPackageBegin += this.PlanPackageBegin;

WiX Burn Bootstrapper Localization

寵の児 提交于 2019-12-04 11:23:18
I have a custom burn bootstrapper application with localization in german (BurnUI_de-DE.wxl) and english (BURNUI_en-US.wxl). At present burn automatically starts in english. I don't know how to change the UI language at run time. The UI parts are designed in MVVM pattern and have a language selection drop down. I have a variable to detect the systemlanguageID like this <Variable Name="INSTALL_LANG" bal:Overridable="yes" Type="string" Value=[SystemLanguageID]"/> Everything is in place. Now, how do I use this variable and instruct the burn engine to change the language? Furthermore, any best

How can I allow MSI features to be selected in a WiX burn bootstrapper?

狂风中的少年 提交于 2019-12-04 10:22:56
问题 I have just started playing around with Burn to try and chain multiple MSI files. I am using WiX v3.6.2705.0. The chaining is working but I'm now trying to get optional features to work. I was hoping that it would just be a case of setting EnableFeatureSelection to "yes" for my MsiPackage tags but it doesn't make any difference whether it is turned on or off. Is there anything else that needs to be done to get optional features working or is this a known issue? Thanks, Alan 回答1: If you want

How to modify the installed features of msi with wix bootstrapper?

前提是你 提交于 2019-12-04 09:50:03
I am trying to call a msi inside wix bootstrapper program.It is working properly at the time of installation.And selected features are installed properly.But after installation i am trying to modify the installed features.In the control panel there is change button.But when i click it then it is showing a dialog with Repair, uninstall, cancel buttons.There is no modify button for modifying the features of installer. Please specify the solution if any. code inside Bootstrappertheme.wxl is <!-- Modify dialog --> <String Id="ModifyHeader">Modify Setup</String> <String Id="ModifyNotice">

How can I upgrade installer WIX bootstrapper bundle via MSI and vice-versa?

China☆狼群 提交于 2019-12-04 05:40:32
The situation: I have a WIX-based bootstrapper installer, which installs my msi package and (some) prerequisites (.NET). The installer is .exe and it works ok. Now, some clients want to install msi, especially in corporate environments where they can push it centrally. It looks easy, just give them the msi. Again, It works ok. Now, the problematic part. When the application is installed from MSI, and later upgraded to newer version from .exe installer, there will be two ARP entries. And vice-versa - when the application is installed from .exe, and later upgraded from MSI, there will be double

How do I install drivers using Burn and DPInst after MSI installation?

痞子三分冷 提交于 2019-12-04 05:28:55
问题 I have a setup MSI for our application, and I also have signed FTDI drivers that need to be installed as well. I'd like for them to be installed with Burn rather than the WiX MSI to keep CustomActions out of the MSI (however, I've tried the CA route as well). I've tried putting the instruction in an ExePackage, but the SourceFile attribute asks for the file location during build, not runtime (e.g. <ExePackage Id="InstallDrivers" DisplayName="Installing Drivers" SourceFile="[InstallFolder

using WIX3.6 to install .NET Framework 3.5 SP1 with Burn

倖福魔咒の 提交于 2019-12-03 19:38:13
问题 I am trying to use Burn and WIX 3.6 to make an installer for my app. The installer must be capable of installing .NET 3.5 SP1 from Microsoft's web site. I am working from a working WIX project created with WIX 3.5. It works, if .NET 3.5 SP1 has been previously installed on the target machine. The first step appears to be to create a bundle, so I added a element to my Product.wxs file. When I do that I get an error saying that the is not valid in the schema, I must have a instead. Does that