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
Hi Edwin,
Thanks for the reply ..
Yes we would like check-in the Heat fragments into over TFS and manage that
file components when ever we add new files to the Main project and make WIX
project setup also part of daily builds.
Can you specify how and where to specify the condition to check for
Jeepers, you should just include the language packs in the products and put a
language selection in the product.
59 language packs is a headache to manage separately.
-Original Message-
From: TimM [mailto:timmay...@smarttech.com]
Sent: 14 March 2013 17:37
To:
David, there are actually a lot of advantages to breaking language packs
out. Servicing in particular can be easier. Burn adds a couple features
(add-on related bundles) that make doing language packs really sweet.
On Fri, Mar 15, 2013 at 8:26 AM, David Watson dwat...@sdl.com wrote:
Jeepers,
DoNotHarvest controls whether the WiX MSBuild scripts will automatically
harvest files in the project for you using the HeatProject task. If my
memory is correct, it is set to True because the current implementation
doesn't harvest something correctly. I think it had something to do with
Can we heat.exe for one on network path like
\\c2tfsci\c$\Builds\16\\Binaries\ContinuousIntegration\_PublishedWebsites\Web.
if so how would be the source path to above location look like in
fragments.wxs?
Thanks in advance..
Chatra
--
View this message in context:
6 matches
Mail list logo
