I have chained multiple Msi/exec packages in my Bundle.wxs. In my managed Bootstrapper code, I would like to get the parameters (such as DisplayName, Vital, etc) of the current package that is being executed. Right now, I have only found events that provide the packageID. Can I use this to somehow access other properties of the package?
相关问题
- How does the setup bootstrapper detect if prerequi
- Wix: How can I set, at runtime, the text to be dis
- Wix variable name formats with spaces and other ch
- WiX: Multiple MSI files?
- Help with one step build all projects + installer
相关文章
- How do I require a value in a textbox in a Wix cus
- How to prevent WiX bundle with same UpgradeCode/Ve
- How do I pass a default 'install location'
- Running msiexec from a service (Local System accou
- Can I use msilib or other Python libraries to extr
- WIX 3.8 msiexec.exe /quiet Error 1603
- Wix Harvest: Same Component/File ID when files are
- Cancel Installation and Rollback using wix burn Bo
Yes. A file called
BootstrapperApplicationData.xml
is created during the build process and included with your Bootstrapper Application. TheBootstrapperApplicationData.xml
has lots of information about the bundle and packages included in yourBundle
Chain
, including theDisplayName
and sizes and vital.You'll find the
BootstrapperApplicationData.xml
right next to your .dll. In managed code you can get it using the following code:In native code, it is easier to use the helper functions provided in the
balutil.lib
. NamelyBalManifestLoad()
thenBalInfoParseFromXml()
to parse the XML file into a bunch of handy structs. You can see the code in src\ext\BalExtension\balutil\balinfo.cpp.Finally, the
BootstrapperApplicationData.xml
can be extended by usingCustomTable
elements and setting theBootstrapperAppplicationData='yes'
attribute.