1. Add following in your script
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense
bal:WixStandardBootstrapperApplication
ThemeFile=SetupTheme.xml
LocalizationFile=SetupTheme.wxl
/
2. Download source and look at the template of theme files at
Better read this article for Burn custom UI
http://neilsleightholm.blogspot.com/2012/10/wix-bootstrapper-application.html
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/General-disccussion-tp7583983p7584027.html
Sent from the wix-users mailing
Read the heat documentation.
Harvest a directory
heat dir .\My Files -gg -sfrag -template:fragment -out directory.wxs
You don't have to install msi to check the effect of Heat params.
See generated SCBUFragment.wxs for details.
Anything included in fragment file will be part of your installation.
filed at
https://sourceforge.net/p/wix/feature-requests/723/
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Gracefully-skip-elevated-packages-for-non-admin-in-bundle-tp7583426p7583496.html
Sent from the wix-users mailing list archive at
SET WIX=toolset-directory
SET WORKING=working-directory
*To harvest*
%WIX%/bin/heat.exe dir %WORKING%\..\exe\plugin -cg pluginFiles -gg -scom
-sreg -sfrag -srd -dr INSTALLLOCATION -var var.PluginProjectDir -out
..\Fragments\pluginFilesFragment.wxs
[You may use/skip -sreg, -sfrag, -dr, -var
Although that was not required but unfortunately I have to *either *put them
on remote location and include them as downloadable payload in setup to
reduce the package size.
*Or *to include them in the package by compressed=yes
--
View this message in context:
There are number of ways of achieving results results.
1) As told by Gabriel
2) Don't include -srd switch to harvest root directory as element.
3) use -var in Heat and -d in candle.
e.g for 3
heat.exe dir $(SolutionDir)MyProject\MyDirectory -ag -sfrag -srd -var
var.MyProjectDir -out
Hi,
I am making a bundle with Burn which chained few packages. It is working
fine for admin users but for non-admin I have few requirements.
Some included packages require elevation but they are not necessary. So for
non-admin I want to just skip them gracefully without asking for elevation.
I
Hi,
I have to install Office XP Primary Interop Assemblies (PIAs) as
prerequisite. I am doing following.
1) Downloading the o2003PIA self extractor.
2)Execute it through and copy to temp folder.
ExePackage
Id=PIA2003_URL
The requirement is to not include it in package to reduce the overall package
size.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Office-XP-Primary-Interop-Assemblies-PIAs-as-prereq-tp7583350p7583352.html
Sent from the wix-users mailing list
Thanks for such a quick response but these options were already declined :(
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Office-XP-Primary-Interop-Assemblies-PIAs-as-prereq-tp7583350p7583354.html
Sent from the wix-users mailing list archive at
Hi
My application requires Word and .Net.
I am creating a wix bootstrap application to install .net if not not found.
The basic criteria i found is to search through registry entries. the
problem is both items may have many products, e.g. Word can have v11, v12,
v14. and .net can have 2.0, 3.5,
12 matches
Mail list logo
