bootstrapper

问题 The questions regarding Bootstrapper & Chaining might have been asked before. I am trying to ask something similar & different . My requirement is to CHAIN 3 installshield msi into a single one and expose the feature selection GUI of 2 of the MSIs as a single feature set such that when the user selects any of the features on the top-level, that selection is passed as parameter(s) to the underlying respective msi & installation continues. User may launch this exe / setup again where he can

问题 I'm struggling with my Custom Bootstrapper Upgrade issue. By following this thread, I'm using LaunchAction.Install. This does Upgrade the Product as well as Boostrapper, but older Bootstrapper remains there, as shown in following screen shot. If I invoke ver 1.0.0.0 from here, it would display Dialog to Install, but would do nothing. However, invoking ver 1.0.1.0 would give me the option to Uninstall the product. However, upon Uninstall, it would only remove itself, and "My Product" is left

问题 <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:util="http://schemas.microsoft.com/wix/UtilExtension"> <Bundle Name="My Test Program" Version="1.0.0.0" Manufacturer="Microsoft" UpgradeCode="cc7cfeae-c3a4-4430-841e-f927de3f9f95"> <BootstrapperApplicationRef Id="WixStandardBootstrapperApplication.RtfLicense" /> <util:RegistrySearch Id="FindDotNet35SP1InstallRegValue" Root="HKLM" Key="SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5" Value="SP"

问题 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

问题 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

问题 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

问题 We are trying to get a custom .NET Bootstrapper to selectively install features in an MSI package through our WiX installer. Having registered to the event PlanMsiFeature we thought that we would be able to access the features in our MSI and exclude certain features based upon preset conditions. The event, however, never appears to be invoked. Has anybody managed to use this event successfully? Many thanks. 回答1: We solved this issue. There were a couple of key items missing. 1) In the Bundle

问题 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:/

问题 I'm creating an installer for a Windows desktop app, which has a dependency on another product that requires .NET 3.5 When installing this on Windows 10, .NET 3.5 is included and has to be enabled in Add/Remove Windows Features. I don't think it is valid to install a downloadable version of .NET 3.5 on Windows 10 (correct me if I'm wrong!). So, is there a way to get WiX to enable the .NET 3.5 "feature" rather than downloading and installing it? 回答1: Not sure whether this is the correct way

问题 I have a bootstrapper that installs a MSI-package. How can i achieve that at least the msi-package-installation gets logged( verbose logging )? And where can i set the log-file-path? Because I won't be able to log everything i guess? And no, i don't want a cmd-solution , i need to implement this into my setup Found LogPathVariable, but don't really know how it works? <MsiPackage SourceFile="$(var.Setup.TargetPath)" LogPathVariable="" /> Googled arround many times and havn't found a solution