Deployment Tools Foundation (DTF) which ships with WiX provides APIs for
working with MSIs (among other things) and querying machine state.
From: Kyle Huey [ksh...@ufl.edu]
Sent: Wednesday, January 13, 2010 7:17 PM
To: General discussion for Windows Instal
You can do it in the inner text of a Property element as CDATA, eg:
Angle Brackets:
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roger Yen
Sent: Monday, April 14, 2008 1:32 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Angle brackets as property value
Hi, I
outside of VS. Is there a problem that
these warnings are causing you or do you just want to be clean?
From: Robert O'Brien
Sent: Friday, April 11, 2008 1:58 PM
To: Jordan Fitzgibbon; 'wix-users@lists.sourceforge.net'
Subject: RE: [WiX-users] format of wix project "suppress speci
ermine the warning number for the warnings that you want to suppress and
then add them to the 1079
field.
From: Robert O'Brien
Sent: Friday, April 11, 2008 12:57 PM
To: Jordan Fitzgibbon; 'wix-users@lists.sourceforge.net'
Subject: RE: [WiX-users] format of wix project "suppress spe
The format is supposed to be:
(;)*
In your case, just put 9 in the text box.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert O'Brien
Sent: Thursday, April 10, 2008 6:01 PM
To: 'wix-users@lists.sourceforge.net'
Subject: [WiX-users] format of wix project "suppress specific war
What errors did you get when you tried to build your MSI *with* the 3 CAs
listed below?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Butcher
Sent: Tuesday, April 08, 2008 9:13 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Reverse engineered VS2003 MSI
Torch is used to create transforms (.mst files) by diffing two MSIs but not
used for instance transforms. If you want to create an MSI with instance
transforms, you can do this in your product authoring with the
and elements. See wix.chm for more details.
Example:
According to wix.chm, comparisons are case-sensitive.
You'll have to use 'Or', eg.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stas Klyachkovsky
Sent: Monday, March 31, 2008 12:53 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] case-insensitive comparison in inclu
I'm not sure how Buildtracker works but I can see a few solutions (in priority
order).
1. The ideal way is to use Candle's -platform switch which sets the preproc
system variable sys.PLATFORM. So you would do something like:
-
-Then call >candle.exe product.wxs -platform [x86|x64|ia64]
Unfortuna
The syntax for ifdef is , not .
So, it would appear that ifdef only checks for preprocessor variables and not
environment variables. Even if you had or any other
existing environment variable, the ifdef wouldn't be working as you'd expect it
to.
Your other approach, won't work because the
p
Can you elaborate a bit more on what "UI elements" you would like to change? Is
that the purpose of creating your patch? Or is it to patch an existing product?
To answer your question on how to use Pyro, Peter Marcu has some blog entries
on how to build an MSP with WiX. You could start here:
ht
You probably want to use the File/@Source attribute. This tells Light where to
pick up your file when it's building the MSI. The file will still get installed
to c:\Program Files\RRHome\RRFoo because your component is nested under that
directory structure.
-Original Message-
From: [EM
I would suggest logging a bug on this. I think that this type of XML validation
shouldn't happen until after pre-processing.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Wednesday, March 19, 2008 11:12 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [
I think you need to either set the INSTALLDIR property or have WorkingDirectory
point to a Directory that you have defined.
Eg.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of YungWei Chen
Sent: Tuesday, February 05, 2008 6:38 PM
To: WixUser
Subject: [WiX-users] How to generate
14 matches
Mail list logo
