bootstrapper

问题 I created a simple bootstrapper for my application using WixSharp. namespace TestBootstrapper { class Program { static void Main() { var package = new MsiPackage("../testmsi.msi") { DisplayInternalUI = true, Id = "MyId", Compressed = true, Visible = true }; var bootstrapper = new Bundle("MyTestInstaller", package) { Version = new Version("1.0.0.0"), UpgradeCode = new Guid("1FCC927B-7BB0-4FB0-B81E-2D87012E470B"), PreserveTempFiles = true, DisableModify = "yes", DisableRemove = true };

问题 I wrote a Boostrapper UI in C# for Net Framework 2.0 using Win-Forms. It started working fine and designed forms are responding as expected. Here is my Wix Bundle Code: <?define TargetFile=$(var.MyBA.TargetDir)$(var.MyBA.TargetFileName)?> <?define BootstrapConfigFile=$(var.MyBA.ProjectDir)BootstrapperCore.config?> <Bundle Name="Bootstrapper1" Version="1.0.0.0" Manufacturer="Farrukh" UpgradeCode="54c4a4a4-dca8-4ae4-b2f4-5e3f3fd8cb92"> <BootstrapperApplicationRef Id=

问题 When using the generic bootstrapper with MSBuild how is the order of installation of prerequisite items determined? For example, given: <Project ToolsVersion="3.5" xmlns='http://schemas.microsoft.com/developer/msbuild/2003'> <ItemGroup> <BootstrapperFile Include='A' /> <BootstrapperFile Include='B' /> <BootstrapperFile Include='C' /> <BootstrapperFile Include='D' /> </ItemGroup> <Target Name='MySetup'> <GenerateBootstrapper Path='C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper'

问题 I'm trying to find a solution for the following issue: I have numerous programs (lets call them slaves) that all rely on a single program (master). I need to distribute an installer for each slave. This installer needs to install the master. I want to be able to version both pieces, so multiple msi's appear to be the right solution, chained with a bootstrapper. My problem is if a slave installer installs the same version of the master that is already installed, the .msi will run in repair

问题 I used WiX 3.7 to write a bootstrapper which installs .net 4.5 first and then my application's MSI: <Chain> <PackageGroupRef Id="NetFx45Redist"/> <MsiPackage Id="MainAppPackage" After="NetFx45Redist" SourceFile="..\bin\Debug\MyApp.msi"/> </Chain> The WiX documentation says that NetFx45Redist is a standalone setup while the NetFx45Web is a web setup. After I built the bootstrapper with Id set to NetFx45Redist it had the same size compared to when I build it with NetFx45Web Id specified. I was

问题 I am writing a Bootstrapper Application and want to create the UI for it using the WixStandardBootstrapperApplication. I want the UI such that on the first page(Install page), I see the standard EULA and a checkbox which says I accept and a button to proceed on the next page (Options page) which should get enabled only after I select the checkbox. On the next page, I list some text and want to have another checkbox, which kind of again says I accept and a button to Install which gets enabled

问题 I'm on WiX 3.7, and I can't get the simple <PackageGroupRef Id="NetFx40Web"/> bundle element to work, as it doesn't bring across the Net FX installer package, or embed it in the setup.exe. I've resorted to creating my own package for this in my Bundle.wxs file, but I am still having trouble. It seems to always try to install .NET 4, even if the machine already has .NET installed. I'm not quite sure of the difference between InstallCondition and DetectCondition . I think InstallCondition is

问题 I've a burn installation whereby the user can select which of three options to install - each one directly relates to one of three MsiPackages in a chain, such as : <Chain> <MsiPackage SourceFile="..\ProductA\bin\Release\ProductA.msi" InstallCondition="chkProductA" /> <MsiPackage SourceFile="..\ProductB\bin\Release\ProductB.msi" InstallCondition="chkProductA" /> <MsiPackage SourceFile="..\ProductC\bin\Release\ProductC.msi" InstallCondition="chkProductC" /> </Chain> All fine. However, when I

问题 I am having problems with hosting a WPF prism app in an ElementHost control and am desparate for help. The PRISM app runs fine in silverlight and in a standalone WPF. The main Shell seems to setup fine in the elementHost on a WinForm however other views only load with the “RegisterViewWithRegion” and not the “Add,Activate” procedure. I need “Add,Activate” for scoping. However I beleive the problem is that I am loading my shell twice … not on purpose. I cannot find a way to call the

问题 I am deploying a .NET application with .NET Framework 4.0 and VS 2010 C++ redistributable as prerequisites. When the setup.exe runs in a machine with the prerequisites satisfied the bootstrapper install them again. Is this a known issue? and what's the correct way to solve it? 回答1: The solution is to edit the bootstrapper product.xml file to contain the correct product code for the Visual Studio C++ Redistributable. See the post below which contains the steps to fix this: Visual C++ 2010