burn

Wix Bootstrapper with large package

瘦欲@ 提交于 2019-12-24 21:16:05
问题 I am using Wix Toolset 3.11 and am attempting to create a Wix bootstrapper that is installing a very large prerequisite to my software - a legacy InstallShield executable with ~5000 associated files found in ~600 folders. I have compressed all these files into a single self-extracting archive that is approximately 3GB. I am getting the following error when attempting to build: light.exe(0,0): error LGHT0001: Arithmetic operation resulted in an overflow. Here is my current relevant XML in the

WIX run second application then first is done

风流意气都作罢 提交于 2019-12-24 18:13:22
问题 I stuck on problem with wix installer. My idea is create .msi installer, and then user install .msi , the setup.exe runs , and then user close this setup.exe(setup will install microsoft add-in) the second one(picture) will be opened sequently. Now this code below runs after checkbox is ticked two aplications both at once. Is the way to run picture only when closed first one ? Please suggest! Here is my code: <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix

Prerequisite bootstrapper application fails to install .NET 4.5

ε祈祈猫儿з 提交于 2019-12-24 05:43:54
问题 My installer has .NET 4.5 as a prerequisite, when running my installer on Vista (with .NET 4.0 installed) it launches the prerequisite bootstrapper as expected. Clicking "Install" moves the dialog to a progress page, and that's where it stops. It just sits at 0% for a while, and then the bootstrapper disappears (exits). Log snippet: [0A30:0360][2013-07-11T10:41:23]i300: Apply begin [093C:06F4][2013-07-11T10:41:23]i360: Creating a system restore point. [093C:06F4][2013-07-11T10:41:28]i361:

Migrate WiX UI to Burn

僤鯓⒐⒋嵵緔 提交于 2019-12-24 03:39:21
问题 I have a working WiX installer with a custom UI using a WixUI_Mondo_MyApp.wxs file. I have to extend my installer to also run another exe installer. I understand Burn is the way to do this. I created a Burn project that chains my original MSI with the custom UI (using DisplayInternalUI="yes"), and that works fine. But I don't want two UIs popping up (the Burn default UI, and my MSI UI), and I need to get some info from the MSI UI to determine if I should install the other exe (it will listed

WiX - passing checkbox values from Burn UI to MSI

做~自己de王妃 提交于 2019-12-24 02:42:38
问题 I have custom UI in Burn with a checkbox "Install Desktop icon". And I have the same thing in my MSI (also created with WiX) that I'm replacing with Burn. The problem is that Burn seems to set checkbox values to 0 or 1 (via MsiProperty ) whereas my MSI expects NULL or NOT NULL . If you try to send through the checkbox value from Burn it will always be evaluated as NOT NULL by the MSI. I have found that I can edit my WiX projects and change: <Condition>DESKTOP_ICONS</Condition> to: <Condition

Adding WIC as a requirement before .NET 4.0 in WiX Burn custom Managed Bootstrapper

ε祈祈猫儿з 提交于 2019-12-23 21:50:22
问题 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

Have WiX/Burn detect the required version of .NET Framework

故事扮演 提交于 2019-12-23 21:12:16
问题 How can I have Burn detect that the required .NET 4.5 framework is installed and if not notify the user prior to launching my custom UI that the install requires .NET 4.5 to run? Without the prerequisite check my custom UI (BootStrapperApplication) will fail to load. I do not want to install only prompt that it is missing. 回答1: In your Bundle.wxs file (or where ever you have the <Bundle> defined), add this: <bal:Condition Message="Add your message here">NETFRAMEWORK40FULL</bal:Condition> For

Wix Bootstrapper: Sequence of Bootstrapper events

偶尔善良 提交于 2019-12-23 09:39:21
问题 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

Is there a WixBundleDirectoryLayout or a /layout sample snippet I can use?

僤鯓⒐⒋嵵緔 提交于 2019-12-23 01:15:19
问题 There is a Burn Built-in Variable - WixBundleDirectoryLayout. How can I assign a value to this variable to change where the bundle extracts to? I also tried running... setup.exe /layout c:\temp ...from a command line and it just copies the setup.exe file to c:\temp, instead of actually extracting the bundle contents. What am I doing wrong? 回答1: The /layout switch does not extract the contents of a Bundle. It downloads all the content and creates an image that you could then burn to DVD or put

Wix Burn: Custom Bootstrapper upgrade but Installs side by side with older version

可紊 提交于 2019-12-22 23:00:16
问题 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