bootstrapper

问题 I have a WinForms project from which I want to open a WPF window from a WPF user control project. But when I create an instance of the WPF window and call Show(), the bootstrapper isn't loaded. In an Windows Application, it's located in the App.xaml, but an user control project doesn't have this. What can I do? Thanks! 回答1: The only thing accomplished by having the bootstrapper in App.xaml's resources is instantiation of the bootstrapper and keeping a reference so it isn't garbage-collected.

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

问题 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 can't find anywhere how to set parameters in the wix bootstrapper so that firewalls and anti-viruses do not treat it as a threat. My bootstrapper on other devices displays information that it is a threat. Or it doesn't start without any information. Edit: I create something like this: <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:fw="http://schemas.microsoft.com/wix/FirewallExtension"> <Bundle Name="Bootstrapper13" Version="1.0.0.0"

问题 I can't find anywhere how to set parameters in the wix bootstrapper so that firewalls and anti-viruses do not treat it as a threat. My bootstrapper on other devices displays information that it is a threat. Or it doesn't start without any information. Edit: I create something like this: <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:fw="http://schemas.microsoft.com/wix/FirewallExtension"> <Bundle Name="Bootstrapper13" Version="1.0.0.0"

问题 I have implemented a custom bootstrapper application (based on this tutorial http://bryanpjohnston.com/2012/09/28/custom-wix-managed-bootstrapper-application/ to install several MSI-files . The UI consists of several XAML-files . I use the ExecuteMsiMessage-event to show the user the current actions: private void OnExecuteMsiMessage(object sender, ExecuteMsiMessageEventArgs e) { lock (this) { this.currentAction = (string)e.Data[0]; } } In the bootstrapper I use a CustomAction to update a VFP

问题 I have a WiX bootstrapper theme xml file, and I want to permanently disable a control. I have tried to set HexStyle to the value of WS_DISABLED (link). However the control is still enabled. Anyone knows if I can use HexStyle or know of another way of having a control permanently disabled. I use the WixStandardBootstrapperApplication.RtfLicense BootstrapperApplication. 回答1: The possible solution is to find Id of this control and then create Variable with postfix "State". I hope it should work:

问题 I've been struggling with the ideal approach to this. Right now, I have my services created in Boostrapper right before I create my application shell, in the method: protected override DependencyObject CreateShell() After my shell gets created, I then create all my view models, passing the services they need. So firstly, I want to know if that's a good practice. Also, I've tried to find examples of declaring services inside a .config file, but I really didn't see any. Is this not a good

问题 I have created a bootstrpper using the dotNetInstaller tool. The created bootstrapper internally has these installers: .NET Framework 4.0 SQL Server Express Now through WiX, what are the steps that I need to follow to invoke the above Bootstrapper from WiX? 回答1: You should not invoke a bootstrapper from WiX - that has no sense. The idea behind the bootstrapper is to "bootstrap" the prerequisites of the installation (.NET and SQL Express in your case) and the main installation package. The