burn

Specify the INSTALLLOCATION of packages in WiX inside the Burn managed bootstrapper

拟墨画扇 提交于 2019-11-28 08:41:50
I have a WiX 3.6 bundle (using Burn ) and managed bootstrapper that install several MSI packages. Some of the packages install to a common location ( C:\program files\MyApp ). I want to let the user choose the install location inside the managed bootstrapper application ( C# WPF , especially because the application is large to install; about 1 GB). How can I specify the INSTALLLOCATION for each MSI packages inside my bundle? Bob Arnson Use an MsiProperty child for each MsiPackage to specify INSTALLLOCATION=[BurnVariable]. Then use Engine.StringVariables to set BurnVariable. For example, in

Multi-Product Shared Component Setup with WiX and MSI?

时光总嘲笑我的痴心妄想 提交于 2019-11-28 05:39:05
问题 Pitch I'm looking for high level advise on how to structure a WiX and Burn MSI based installer solution for an application suite. Question Given the layout below how many distinct MSI packages should an installer suite utilize when all apps/features and shared libs go into the same installation directory? One single MSI package for the whole suite is clearly too large (as shown by the current system) One (complete) MSI package per application would duplicate the dll libraries shared between

Bundle multiple support files for WiX Burn

余生颓废 提交于 2019-11-28 04:58:52
问题 I have a third party MSI that has been supplied to me by a vendor. However the MSI does not stand alone, it requires multiple support files (dll's, config files, device drivers ...) to complete an installation. I've tried to install without these files present in the directory with the MSI and it complains about the missing files during installation. Seems to me this is an odd way to build an installer. Anyway, I'd like to bundle this "installation" to be consumed by Burn. I've used

Custom WiX Burn bootstrapper user interface?

非 Y 不嫁゛ 提交于 2019-11-28 02:54:04
I'm creating an installation package with WiX 3.6 primarily so I can take advantage of the Burn bootstrapping features. So far I have several MSI packages bundled together that will be installed with the built-in bootstrapper application ( WixStandardBootstrapperApplication.RtfLicense ). I have read that Burn allows the default bootstrapper application to be replaced by specifying a custom UX.dll , but I haven't yet been able to locate any resources that describes how the custom ux.dll is constructed (that is, how it integrates with the Burn engine, what technologies do I use, what interfaces

WIX Burn Uninstallation?

蹲街弑〆低调 提交于 2019-11-28 00:29:03
问题 I have a WIX_bundle (V1.0.0.0) which installs 4 third party MSI's of the version (5.0.0.0). Now the new version of my third party MSI's got updated (6.0.0.0). I created a new version of the WIX_Bundle with (v2.0.0.0) and both the WIX bundles have the same upgrade code. What I want to happen is that the new version of the WIX_Bundle should uninstall the previous version (v1.0.0.0 along with the 4 MSI's) and install the new version (v2.0.0.0 with new 4 MSI's). But when I try to install the WIX

Wix & Burn - Install IIS if not yet installed

三世轮回 提交于 2019-11-27 15:21:54
问题 I've a project using IIS, and I want to create an installer for it with Wix. I've created the .msi installer for the app successfully, and I'm creating a Bundle installer for it, which will install the prerequisites and after that my application. Here's the Bundle's code: <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:util="http://schemas.microsoft.com/wix/UtilExtension" xmlns:bal="http://schemas.microsoft.com/wix/BalExtension"> <Bundle Name

Wix Burn vcredist

久未见 提交于 2019-11-27 11:40:24
问题 I have a c++ application developed using Visual Studio 2015, along with a Wix installer and a Burn bootstrapper. Previous versions of the application were able to use the Visual Studio merge module to install the necessary prerequisites, but it appears that this isn't an option when using Visual Studio 2015 (see Redistributables for deploying C++ exe developed with Visual Studio 2015 on Windows 7). Following the advice in that link, we have started installing vcredist with Burn using an

Wix burn doesn't allow to remove file

痞子三分冷 提交于 2019-11-27 08:53:25
问题 I'm creating a bootsrapper and I want to remove links that are created during installation. So I write following step: <Chain> ... <ExePackage Id="removelnk" Cache="no" SourceFile="run.bat" InstallCommand="del "C:\Users\Public\Desktop\Parity UI.lnk"" /> </Chain> Where run.bat is simply %* which allows to run arbitrary code as described here. However, it doesn't work: [19EC:0E2C][2018-06-16T18:32:27]i301: Applying execute package: removelnk, action: Install, path: C:\ProgramData\Package Cache

What is the best practice to create MSI with some other child MSI as prerequisite?

落花浮王杯 提交于 2019-11-27 06:44:56
问题 Currently we are using Inno Setup as a bootstrapper to install the MSI prerequisites. It makes bit complex to maintain the setup. I found the Burn tool which may help us to resolve this issue by having a single setup to install whatever we need. I could not find either documentation or sample for this tool. Is anyone have idea about this? Or is there an alternative solutio? I am looking for the alternative solution for the actions that we do with the ISS bootstrapper now: Extract the files

WIX Installer with modern look and feel

不羁的心 提交于 2019-11-27 05:32:41
I am currently creating an installer for my software. I decided to use WIX for it, because I read on stackoverflow that while it has a steep learning curve, it is the most versatile tool to create .msi installers. I'm trying to create a very simple one screen installer, and I'm happy with the results so far, but some of the controls just look really outdated. The sunken text edit doesn't really match the look and feel of Windows 10. What bothers me more is the file browsing dialog, though. I know that I can change the logo, but the icons and everything just look like they're coming from