Check out src\Setup\Msi\Lux.wxs or src\Setup\Msi\VStudio.wxs from wix
sources for a working sample:
Component Id=VSSchema2005
Guid=7150C0A6-5626-48B6-AA4C-671754E22706 KeyPath=yes Win64=no
Directory=TARGETDIR
CopyFile Id=CopyWixSchema2005
DestinationProperty=VS2005_SCHEMAS_DIR FileId=wix.xsd /
I am out of the office until 04/14/2011.
I will be out of the office, with limited email and phone access.
Note: This is an automated response to your message Re: [WiX-users] CopyFile
with pattern doesn't copy files - it looks like it doesn't do anything
at all! sent on 4/13/2011 2:44:00 AM.
Try to use condition UPGRADE_FROM_VERSION = 6.1.8.85. Not sure it will fix
your problem. Better approach is to use Upgrade element to find previous
versions of your product, and then use properties which are set by
FindRelatedProducts.
-Maksim
-Original Message-
From: Greg
Hello everyone,
Is there anything documented on how to build multiple patches using purely WiX?
I need to create a patch that should apply to multiple installed instances for
a given product.
Thanks
Eugen
-
This
Hi!
I am having trouble associating multiple file types with one exe file.
I want my program to handle multiple file types. My code is as follows...
However, it does not register properly file types in Windows.
Can you help?
Thanks
Component Id=SMVExe Guid=SOME GUID
File Id=SMVExeFile
I'm not sure I understand Maksim - the current value of UPGRADE_FROM_VERSION
is 6.1.8.78, and the condition is UPGRADE_FROM_VERSION = 6.1.8.85
(ignoring AND InstallModeRemove for the moment). You are saying to
try the condition UPGRADE_FROM_VERSION = 6.1.8.85, which is no
different from what I
Here is the situation. I have a configuration file that on installation in
release mode I use the XmlFile task to remove a section of the file. In debug I
also use XmlFile to modify one of the elements in the file. Is what I am
finding is that if I do a release installation followed by a debug
Check a verbose log file and it should say why it is not replacing that
file. Typically because it is newer than the file you hope to replace it
with.
The RemoveFile element can be handy for some of these types of issues.
Not positive it's what you'll want, but maybe.
-Original
The log file looks like:
MSI (s) (6C:EC) [13:54:36:297]: Executing op:
Yes. I run into this with text files (xml mostly) a lot. RemoveFile can
go under the same Component as the File element. That's the way I always
use it.
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, April 13, 2011 12:21 PM
To: General discussion
I add RemoveFile but on uninstall. This gave me the same error do you
usually specify both for this kind of situation?
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Chad Petersen
I cannot seem to get RemoveFile to work. Here is my latest attempt:
Component Id=CMP_WpfAppConfig Guid=* Directory=WPFINSTALLDIR
File Id=FILE_WpfAppConfig
Source=../WPFHost/app.Config
KeyPath=yes/
RemoveFile Id=WpfAppConfig0
I only ever specify On=install.
I think of it as asking the install to remove the existing file, no
matter what, prior to copying in the new file. I equate this to the
InstallShield Always Overwrite setting.
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent:
My syntax is a bit different than yours, but you might try removing the
[WPFINSTALLDIR] property from your RemoveFile element. But, I always
nest my Components under a Directory element, so our approach is
somewhat different.
-Original Message-
From: Kevin Burton
14 matches
Mail list logo