bootstrapper

问题 I updated Ninject.MVC3 package from 2.2.1.0 to 2.2.2.0. Before I had access to the Kernel object through BootStrapper.Kernel property but in the new version Kernel property is marked as obsolete. I get a warning saying 'Public ReadOnly Property Kernel As Ninject.IKernel' is obsolete: 'Do not use Ninject as Service Locator'. Is there a different way to access the kernel in the new version? 回答1: The reason why this has been marked Obsolete and will be changed to internal in future is that

问题 I'm looking at using Burn as a bootstrapper for an installer and I need to pass in a couple of arguments into the MSI. I know that the way to do this is to use MsiProperty elements, the issue I am having is with displaying the UI to capture those properties. I'm aware that I can create a completely custom UI via the managed bootstrapper application host, however this is turning out to be a lot of work to implement for a relatively minor tweak to the bootstrapper. I've found this blog article

问题 I am making a package installer and am followin the KISS principle. No bundle made in WiX 3.6-3.8 works on Windows XP (but works as expected in Windows 7). The cause is elevation error 0x800705b4. [14DC:15A8][2014-02-12T11:54:46]e000: Error 0x800705b4: Failed to wait for child to connect to pipe. [14DC:15A8][2014-02-12T11:54:46]e000: Error 0x800705b4: Failed to connect to elevated child process. [14DC:15A8][2014-02-12T11:54:46]e000: Error 0x800705b4: Failed to actually elevate. [14DC:15A8]

问题 In my MVVM based Wix Managed Bootstrapper application, while handling different events, I'm trying to show the user a view to get some input. It looks like Burn events are executing Asynchronously because using Dispatcher.Invoke(), it is skipping or passing by the view and hitting the last event, i.e not waiting for this input task to finish. Here is the event handler which needs to finish before hitting last one: Please note that when MessageBox.Show is popped, it waits until we close it.

问题 I already posted a related problem here: Wix: Managed BA command line not effective, which is about command line passed during upgrade. Now I tried to explore, how it interpret the command line. Here is my run method to do so: protected override void Run() { string cmdOptions = string.Empty; this.Engine.Log(LogLevel.Verbose, "Launching custom TestBA UX"); Debug.WriteLine("Command.Display: {0} Command.Action: {1}", this.Command.Display.ToString(), this.Command.Action.ToString()); Environment

问题 I have a WiX installer and a number of bootstrappers. We recently added SQL LocalDB support and found we needed to package .Net 4.0.2 to get it to work. I am now testing on Windows 8, and find that this patch fails and isn't actually needed for this OS. However, my installer fails because .Net 4.0.2 fails. I am trying to find a way of either skipping this patch in Windows 8 or just ignoring a fail for this patch? I have " InstallConditions " and " ExitCodes " in my package.xml , but I don't

问题 I'm running Visual Studio 2008 SP1, and I'm getting the following error when trying to compile my WiX projct: Could not find required file 'setup.bin' in 'C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Engine I've got Windows Installer 3.0 and the Windows Platform SDK installed. I've got a Microsoft SDKs\Windows\v6.0A directory, but there is no Boostrapper directory. Where can I get this? 回答1: Which Windows SDK do you have installed? I installed this one a few months back and it

问题 I've built an installer with WIX and have packaged it with the .NET 4.0 framework using the GenerateBootstrapper task. Now .NET 4.0 cannot be installed on XP SP2, but it appears to have no precondition check for this so its installer fails halfway through. I'd like to add my own check to make sure the OS that the entire package is being installed on is supported by the .NET 4.0 framework. Is there a way to embed an OS/Service Pack check in the bootstrapper when you use GenerateBootstrapper ?

问题 I'm having trouble getting a burn bundle with a custom managed bootstrapper application to launch on certain platforms that do not come with Windows Imaging Component, which is required to install .NET 4.0 (Windows 2003 being one of them). We are using the standard method of defining what the managed bootstrapper application requires: <WixVariable Id="WixMbaPrereqPackageId" Value="Netfx4Full"/> When this bootstrapper is run on a newly installed Windows 2003 R2 machine, it launches the

问题 I've started playing with Managed Boostrapper Classes and events. Making story short, I've added BoostrapperCore.dll and it would give you the namespace Microsoft.Tools.WindowsInstallerXml.Bootstrapper I was able to get some info from some examples present in different blogs. For instance, the Entry point is BootstrapperApplication.Run() , is called when bootstrapper application is ready to run. Then there are events like: BoostrapperApplication.DetectBegin BoostrapperApplication