Re: [WiX-users] CopyFile with pattern doesn't copy files - it looks like it doesn't do anything at all!
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 / ... /Component At first glance Component/@Directory is sourcedir and Component/CopyFile/@DestinationProperty destinationdir... 2011/4/13 Amber Scouras amber.scou...@thetradedesk.com: I'm using WiX 3.5 (an RC from late in 2010). My core problem is that I have an installer that needs to deploy the same files to multiple Components. In this thread on StackOverflow (http://stackoverflow.com/questions/4941602/features-installed-to-different-locations-but-referencing-the-same-components), Rob Mensching states: A Component can only be installed once via an MSI. Each Component can only be installed to a single Directory. To have the contents of a Component installed to two different locations, you either have to create another Component with the same content or try to use the CopyFile element to duplicate the content. The files are referenced in the .wxs via a .wxi include, which means their Id properties are static. I tried various methods of namespacing these Ids at include time, but that didn't work for various reasons (I can go into these if necessary, but would prefer not to for brevity). So, for now, I've eliminated the possibility of duplicating the File elements per Component. That leaves me with just the CopyFile option. I created a new Component for the shared files that installs to its own directory and I added a single CopyFile element (using a pattern of * in the SourceName attribute) to each of the existing Components that should copy the files. The new Component installs correctly but, unfortunately, the CopyFile elements seem to do nothing. The files just don't copy. In trying to debug the issue, I installed with msiexec from the command line with full logging (/lvx*) and could find no trace of relevant file copy logging. Without any indication of what I'm doing wrong, I can't debug the problem and I'm hoping somebody on this list can help me. Here are the approaches I've tried so far (none have worked): First Approach Use CopyFile's SourceDirectory and DestinationDirectory attributes with a SourceName pattern. Note that I've also tried with a pattern of *.*, a pattern of .*, pattern of *.dll, and without a pattern (specifying a single specific file to be copied), which also did not work. Directory Id =ROOT_INSTALL_DIR Directory Id =SERVICES_DIR Name =Services Directory Id=SHARED_BINARIES_DIR Name=Binaries Component Id=SharedBinaries Guid=49779A88-652A-11E0-AE98-1EF2DFD72085 ?include $(var.BUILD_DIR)\Shared.wxi ? /Component /Directory Directory Id =SERVICE_ONE_DIR Name=ServiceOne Component Id=ServiceOneComponent Guid=C743A1E6-7E71-4196-979F-F3218421BCCE CopyFile Id=ServiceOneSharedBinaries SourceDirectory=SHARED_BINARIES_DIR SourceName=* DestinationDirectory=SERVICE_ONE_DIR/ /Component /Directory !-- More services with similar CopyFile elements -- /Directory /Directory Feature Id=SharedBinariesFeature Level=1 ComponentRef Id=SharedBinaries / /Feature Feature Id=ServiceOneFeature Level=1 ComponentRef Id=ServiceOneComponent/ /Feature Second Approach Use SourceProperty and DestinationProperty attributes instead of the *Directory attributes. Directory Id =ROOT_INSTALL_DIR Directory Id =SERVICES_DIR Name =Services Directory Id=SHARED_BINARIES_DIR Name=Binaries Component Id=SharedBinaries Guid=49779A88-652A-11E0-AE98-1EF2DFD72085 ?include $(var.BUILD_DIR)\Shared.wxi ? /Component /Directory Directory Id =SERVICE_ONE_DIR Name=ServiceOne Component Id=ServiceOneComponent Guid=C743A1E6-7E71-4196-979F-F3218421BCCE CopyFile Id=ServiceOneSharedBinaries SourceProperty=SHARED_BINARIES_DIR SourceName=* DestinationProperty=SERVICE_ONE_DIR/ /Component /Directory !-- More services with similar CopyFile elements -- /Directory /Directory Feature Id=SharedBinariesFeature Level=1 ComponentRef Id=SharedBinaries / /Feature Feature Id=ServiceOneFeature Level=1 ComponentRef Id=ServiceOneComponent/ /Feature Third Approach Explicitly create new properties with CustomActions and use those properties in SourceProperty and DestinationProperty - this seemed silly and redundant, but it appears that it worked in this thread (http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CopyFile-doesn-t-work-td2592289.html). From the install log, I can tell
[WiX-users] AUTO: Kenneth L Resler is out of the office. (returning 04/14/2011)
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. This is the only notification you will receive while this person is away. Disclaimer: Information in this message or an attachment may be government data and thereby subject to the Minnesota Government Data Practices Act, Minnesota Statutes, Chapter 13, may be subject to attorney-client or work product privilege, may be confidential, privileged, proprietary, or otherwise protected, and the unauthorized review, copying, retransmission, or other use or disclosure of the information is strictly prohibited. If you are not the intended recipient of this message, please immediately notify the sender of the transmission error and then promptly delete this message from your computer system. -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Component condition question
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 [mailto:g...@swansonsoftware.com] Sent: Tuesday, April 12, 2011 11:53 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Component condition question Thanks Maksim. ThE uPGRADE_FROM_VERSION property is set to 6.1.8.78, which is the value I expected to see. The log shows uPGRADE_FROM_VERSION being set. Here's an example: MSI (s) (94!D0) [11:04:09:292]: PROPERTY CHANGE: Modifying UPGRADE_FROM_VERSION property. Its current value is '9.9.9.9'. Its new value: '6.1.8.78'. Greg -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Component-condition-question-tp6263309p6266492.html Sent from the wix-users mailing list archive at Nabble.com. -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Building multiple patches using purely WiX
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 transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to register multiple file types - Multiple ProgId
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 Name=$(var.SMV.TargetFileName) Source=$(var.SMV.TargetPath) DiskId=1 KeyPath=yes Shortcut Id=startmenuShortcutSMV Directory=ProgramMenuDir Name=S2 MV WorkingDirectory=INSTALLLOCATION Icon=SMVIcon.exe IconIndex=0 Advertise=yes / Shortcut Id=desktopShortcutSMV Directory=DesktopFolder Name=S2 MV WorkingDirectory=INSTALLLOCATION Icon=SMVIcon.exe IconIndex=0 Advertise=yes / /File !-- Register file associations in Windows -- ProgId Id=SMV.mvwFile Description=S2 MV Workspace document Advertise=yes Icon=IconMvwDoc.ico Extension Id=mvw ContentType=application/mvw Verb Id=open Command=Open Argument=%1 / /Extension /ProgId ProgId Id=SMV.mveFile Description=S2 MV Export document Advertise=yes Icon=IconMveDoc.ico Extension Id=mve ContentType=application/mve Verb Id=open Command=Open Argument=%1 / /Extension /ProgId ProgId Id=SMV.s2eFile Description=SEP2 Manager Export document Advertise=yes Icon=IconS2eDoc.ico Extension Id=s2e ContentType=application/s2e Verb Id=open Command=Open Argument=%1 / /Extension /ProgId /Component -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Component condition question
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 have except for double quotes around the property name. I would like to use the approach you are suggesting but can't, FindRelatedProducts doesn't run during maintenance mode. Thanks, Greg -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Component-condition-question-tp6263309p6270119.html Sent from the wix-users mailing list archive at Nabble.com. -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX force copy file.
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 installation the element that I am looking for is not found and the installation fails. If I look at the configuration file the section is missing. I was expecting the whole file to be copied to the installation folder (overwriting the release edited file) before I try the debug editing but apparently that is not happening. Is there some rule within WiX that it will not overwrite a file if it exists? If so can I override this behavior? The applicable WiX code looks like: Component Id=CMP_WpfAppConfig Guid=* Directory=WPFINSTALLDIR File Id=FILE_WpfAppConfig Source=../WPFHost/app.Config KeyPath=yes/ . . . . . ?if $(var.Configuration) = Debug ? util:XmlFile Id=WpfAppConfig14 File=[WPFINSTALLDIR]app.Config Action=setValue Name=initializeData Value=f:\applog\app_tracelog.svclog ElementPath=//configuration/system.diagnostics/sharedListeners/add[\[]@name=quot;ServiceModelTraceListenerquot;[\]] Sequence=14 / ?endif ? ?if $(var.Configuration) = Release ? util:XmlConfig Id=WpfAppConfig15 Action=delete ElementPath=//configuration File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=15 VerifyPath=system.diagnostics / util:XmlConfig Id=WpfAppConfig16 Action=delete ElementPath=//configuration/system.serviceModel File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=16 VerifyPath=diagnostics / ?endif ? Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.commailto:kev...@buyseasons.com -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX force copy file.
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 Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, April 13, 2011 11:37 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WiX force copy file. 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 installation the element that I am looking for is not found and the installation fails. If I look at the configuration file the section is missing. I was expecting the whole file to be copied to the installation folder (overwriting the release edited file) before I try the debug editing but apparently that is not happening. Is there some rule within WiX that it will not overwrite a file if it exists? If so can I override this behavior? The applicable WiX code looks like: Component Id=CMP_WpfAppConfig Guid=* Directory=WPFINSTALLDIR File Id=FILE_WpfAppConfig Source=../WPFHost/app.Config KeyPath=yes/ . . . . . ?if $(var.Configuration) = Debug ? util:XmlFile Id=WpfAppConfig14 File=[WPFINSTALLDIR]app.Config Action=setValue Name=initializeData Value=f:\applog\app_tracelog.svclog ElementPath=//configuration/system.diagnostics/sharedListeners/add[\[]@ name=quot;ServiceModelTraceListenerquot;[\]] Sequence=14 / ?endif ? ?if $(var.Configuration) = Release ? util:XmlConfig Id=WpfAppConfig15 Action=delete ElementPath=//configuration File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=15 VerifyPath=system.diagnostics / util:XmlConfig Id=WpfAppConfig16 Action=delete ElementPath=//configuration/system.serviceModel File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=16 VerifyPath=diagnostics / ?endif ? Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.commailto:kev...@buyseasons.com -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX force copy file.
The log file looks like: MSI (s) (6C:EC) [13:54:36:297]: Executing op: FileCopy(SourceName=dfl-c3lj.con|app.Config,SourceCabKey=FILE_ServiceAppConfig,DestName=app.Config,Attributes=512,FileSize=32206,PerTick=32768,,VerifyMedia=1,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPart1=-680126199,HashPart2=1248668224,HashPart3=-1650872411,HashPart4=1522490087,,) MSI (s) (6C:EC) [13:54:36:297]: File: D:\Program Files (x86)\BsiServices\ServiceHost\app.Config;Won't Overwrite;Won't patch;Existing file is unversioned but modified I will look at RemoveFile. It seems kind of counter intuitive that on installation I want to remove a file. Would I put the RemoveFile element in the same component as the component that is installing the file? -Original Message- From: Chad Petersen [mailto:chad.peter...@harlandfs.com] Sent: Wednesday, April 13, 2011 2:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. 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 Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, April 13, 2011 11:37 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WiX force copy file. 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 installation the element that I am looking for is not found and the installation fails. If I look at the configuration file the section is missing. I was expecting the whole file to be copied to the installation folder (overwriting the release edited file) before I try the debug editing but apparently that is not happening. Is there some rule within WiX that it will not overwrite a file if it exists? If so can I override this behavior? The applicable WiX code looks like: Component Id=CMP_WpfAppConfig Guid=* Directory=WPFINSTALLDIR File Id=FILE_WpfAppConfig Source=../WPFHost/app.Config KeyPath=yes/ . . . . . ?if $(var.Configuration) = Debug ? util:XmlFile Id=WpfAppConfig14 File=[WPFINSTALLDIR]app.Config Action=setValue Name=initializeData Value=f:\applog\app_tracelog.svclog ElementPath=//configuration/system.diagnostics/sharedListeners/add[\[]@ name=quot;ServiceModelTraceListenerquot;[\]] Sequence=14 / ?endif ? ?if $(var.Configuration) = Release ? util:XmlConfig Id=WpfAppConfig15 Action=delete ElementPath=//configuration File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=15 VerifyPath=system.diagnostics / util:XmlConfig Id=WpfAppConfig16 Action=delete ElementPath=//configuration/system.serviceModel File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=16 VerifyPath=diagnostics / ?endif ? Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.commailto:kev...@buyseasons.com -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo
Re: [WiX-users] WiX force copy file.
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 for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. The log file looks like: MSI (s) (6C:EC) [13:54:36:297]: Executing op: FileCopy(SourceName=dfl-c3lj.con|app.Config,SourceCabKey=FILE_ServiceApp Config,DestName=app.Config,Attributes=512,FileSize=32206,PerTick=32768,, VerifyMedia=1,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPa rt1=-680126199,HashPart2=1248668224,HashPart3=-1650872411,HashPart4=1522 490087,,) MSI (s) (6C:EC) [13:54:36:297]: File: D:\Program Files (x86)\BsiServices\ServiceHost\app.Config; Won't Overwrite; Won't patch;Existing file is unversioned but modified I will look at RemoveFile. It seems kind of counter intuitive that on installation I want to remove a file. Would I put the RemoveFile element in the same component as the component that is installing the file? -Original Message- From: Chad Petersen [mailto:chad.peter...@harlandfs.com] Sent: Wednesday, April 13, 2011 2:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. 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 Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, April 13, 2011 11:37 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WiX force copy file. 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 installation the element that I am looking for is not found and the installation fails. If I look at the configuration file the section is missing. I was expecting the whole file to be copied to the installation folder (overwriting the release edited file) before I try the debug editing but apparently that is not happening. Is there some rule within WiX that it will not overwrite a file if it exists? If so can I override this behavior? The applicable WiX code looks like: Component Id=CMP_WpfAppConfig Guid=* Directory=WPFINSTALLDIR File Id=FILE_WpfAppConfig Source=../WPFHost/app.Config KeyPath=yes/ . . . . . ?if $(var.Configuration) = Debug ? util:XmlFile Id=WpfAppConfig14 File=[WPFINSTALLDIR]app.Config Action=setValue Name=initializeData Value=f:\applog\app_tracelog.svclog ElementPath=//configuration/system.diagnostics/sharedListeners/add[\[]@ name=quot;ServiceModelTraceListenerquot;[\]] Sequence=14 / ?endif ? ?if $(var.Configuration) = Release ? util:XmlConfig Id=WpfAppConfig15 Action=delete ElementPath=//configuration File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=15 VerifyPath=system.diagnostics / util:XmlConfig Id=WpfAppConfig16 Action=delete ElementPath=//configuration/system.serviceModel File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=16 VerifyPath=diagnostics / ?endif ? Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.commailto:kev...@buyseasons.com -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users --
Re: [WiX-users] WiX force copy file.
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 [mailto:chad.peter...@harlandfs.com] Sent: Wednesday, April 13, 2011 2:25 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. 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 for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. The log file looks like: MSI (s) (6C:EC) [13:54:36:297]: Executing op: FileCopy(SourceName=dfl-c3lj.con|app.Config,SourceCabKey=FILE_ServiceApp Config,DestName=app.Config,Attributes=512,FileSize=32206,PerTick=32768,, VerifyMedia=1,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPa rt1=-680126199,HashPart2=1248668224,HashPart3=-1650872411,HashPart4=1522 490087,,) MSI (s) (6C:EC) [13:54:36:297]: File: D:\Program Files (x86)\BsiServices\ServiceHost\app.Config; Won't Overwrite; Won't patch;Existing file is unversioned but modified I will look at RemoveFile. It seems kind of counter intuitive that on installation I want to remove a file. Would I put the RemoveFile element in the same component as the component that is installing the file? -Original Message- From: Chad Petersen [mailto:chad.peter...@harlandfs.com] Sent: Wednesday, April 13, 2011 2:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. 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 Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, April 13, 2011 11:37 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WiX force copy file. 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 installation the element that I am looking for is not found and the installation fails. If I look at the configuration file the section is missing. I was expecting the whole file to be copied to the installation folder (overwriting the release edited file) before I try the debug editing but apparently that is not happening. Is there some rule within WiX that it will not overwrite a file if it exists? If so can I override this behavior? The applicable WiX code looks like: Component Id=CMP_WpfAppConfig Guid=* Directory=WPFINSTALLDIR File Id=FILE_WpfAppConfig Source=../WPFHost/app.Config KeyPath=yes/ . . . . . ?if $(var.Configuration) = Debug ? util:XmlFile Id=WpfAppConfig14 File=[WPFINSTALLDIR]app.Config Action=setValue Name=initializeData Value=f:\applog\app_tracelog.svclog ElementPath=//configuration/system.diagnostics/sharedListeners/add[\[]@ name=quot;ServiceModelTraceListenerquot;[\]] Sequence=14 / ?endif ? ?if $(var.Configuration) = Release ? util:XmlConfig Id=WpfAppConfig15 Action=delete ElementPath=//configuration File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=15 VerifyPath=system.diagnostics / util:XmlConfig Id=WpfAppConfig16 Action=delete ElementPath=//configuration/system.serviceModel File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=16 VerifyPath=diagnostics / ?endif ? Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.commailto:kev...@buyseasons.com -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010
Re: [WiX-users] WiX force copy file.
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 Name=[WPFINSTALLDIR]app.Config On=both/ . !-- -- ?if $(var.Configuration) = Debug ? util:XmlFile Id=WpfAppConfig14 File=[WPFINSTALLDIR]app.Config Action=setValue Name=initializeData Value=f:\applog\app_tracelog.svclog ElementPath=//configuration/system.diagnostics/sharedListeners/add[\[]@name=quot;ServiceModelTraceListenerquot;[\]] Sequence=14 / ?endif ? ?if $(var.Configuration) = Release ? util:XmlConfig Id=WpfAppConfig15 Action=delete ElementPath=//configuration File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=15 VerifyPath=system.diagnostics / util:XmlConfig Id=WpfAppConfig16 Action=delete ElementPath=//configuration/system.serviceModel File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=16 VerifyPath=diagnostics / ?endif ? . /Component I still get the error message in the log below. The error message indicates that the file is unversioned but modified. Hopefullly applying RemoveFile correctly will let me essentially overwrite the file. Thank you. -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, April 13, 2011 12:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. The log file looks like: MSI (s) (6C:EC) [13:54:36:297]: Executing op: FileCopy(SourceName=dfl-c3lj.con|app.Config,SourceCabKey=FILE_ServiceApp Config,DestName=app.Config,Attributes=512,FileSize=32206,PerTick=32768,, VerifyMedia=1,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPa rt1=-680126199,HashPart2=1248668224,HashPart3=-1650872411,HashPart4=1522 490087,,) MSI (s) (6C:EC) [13:54:36:297]: File: D:\Program Files (x86)\BsiServices\ServiceHost\app.Config; Won't Overwrite; Won't patch;Existing file is unversioned but modified I will look at RemoveFile. It seems kind of counter intuitive that on installation I want to remove a file. Would I put the RemoveFile element in the same component as the component that is installing the file? -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX force copy file.
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: Wednesday, April 13, 2011 12:37 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. 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 [mailto:chad.peter...@harlandfs.com] Sent: Wednesday, April 13, 2011 2:25 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. 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 for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. The log file looks like: MSI (s) (6C:EC) [13:54:36:297]: Executing op: FileCopy(SourceName=dfl-c3lj.con|app.Config,SourceCabKey=FILE_ServiceApp Config,DestName=app.Config,Attributes=512,FileSize=32206,PerTick=32768,, VerifyMedia=1,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPa rt1=-680126199,HashPart2=1248668224,HashPart3=-1650872411,HashPart4=1522 490087,,) MSI (s) (6C:EC) [13:54:36:297]: File: D:\Program Files (x86)\BsiServices\ServiceHost\app.Config; Won't Overwrite; Won't patch;Existing file is unversioned but modified I will look at RemoveFile. It seems kind of counter intuitive that on installation I want to remove a file. Would I put the RemoveFile element in the same component as the component that is installing the file? -Original Message- From: Chad Petersen [mailto:chad.peter...@harlandfs.com] Sent: Wednesday, April 13, 2011 2:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. 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 Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, April 13, 2011 11:37 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WiX force copy file. 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 installation the element that I am looking for is not found and the installation fails. If I look at the configuration file the section is missing. I was expecting the whole file to be copied to the installation folder (overwriting the release edited file) before I try the debug editing but apparently that is not happening. Is there some rule within WiX that it will not overwrite a file if it exists? If so can I override this behavior? The applicable WiX code looks like: Component Id=CMP_WpfAppConfig Guid=* Directory=WPFINSTALLDIR File Id=FILE_WpfAppConfig Source=../WPFHost/app.Config KeyPath=yes/ . . . . . ?if $(var.Configuration) = Debug ? util:XmlFile Id=WpfAppConfig14 File=[WPFINSTALLDIR]app.Config Action=setValue Name=initializeData Value=f:\applog\app_tracelog.svclog ElementPath=//configuration/system.diagnostics/sharedListeners/add[\[]@ name=quot;ServiceModelTraceListenerquot;[\]] Sequence=14 / ?endif ? ?if $(var.Configuration) = Release ? util:XmlConfig Id=WpfAppConfig15 Action=delete ElementPath=//configuration File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=15 VerifyPath=system.diagnostics / util:XmlConfig Id=WpfAppConfig16 Action=delete ElementPath=//configuration/system.serviceModel File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=16 VerifyPath=diagnostics / ?endif ? Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.commailto:kev...@buyseasons.com -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this
Re: [WiX-users] WiX force copy file.
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 [mailto:kev...@buyseasons.com] Sent: Wednesday, April 13, 2011 12:54 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] WiX force copy file. 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 Name=[WPFINSTALLDIR]app.Config On=both/ . !-- -- ?if $(var.Configuration) = Debug ? util:XmlFile Id=WpfAppConfig14 File=[WPFINSTALLDIR]app.Config Action=setValue Name=initializeData Value=f:\applog\app_tracelog.svclog ElementPath=//configuration/system.diagnostics/sharedListeners/add[\[]@ name=quot;ServiceModelTraceListenerquot;[\]] Sequence=14 / ?endif ? ?if $(var.Configuration) = Release ? util:XmlConfig Id=WpfAppConfig15 Action=delete ElementPath=//configuration File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=15 VerifyPath=system.diagnostics / util:XmlConfig Id=WpfAppConfig16 Action=delete ElementPath=//configuration/system.serviceModel File=[WPFINSTALLDIR]app.Config Node=element On=install Sequence=16 VerifyPath=diagnostics / ?endif ? . /Component I still get the error message in the log below. The error message indicates that the file is unversioned but modified. Hopefullly applying RemoveFile correctly will let me essentially overwrite the file. Thank you. -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, April 13, 2011 12:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX force copy file. The log file looks like: MSI (s) (6C:EC) [13:54:36:297]: Executing op: FileCopy(SourceName=dfl-c3lj.con|app.Config,SourceCabKey=FILE_ServiceApp Config,DestName=app.Config,Attributes=512,FileSize=32206,PerTick=32768,, VerifyMedia=1,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPa rt1=-680126199,HashPart2=1248668224,HashPart3=-1650872411,HashPart4=1522 490087,,) MSI (s) (6C:EC) [13:54:36:297]: File: D:\Program Files (x86)\BsiServices\ServiceHost\app.Config; Won't Overwrite; Won't patch;Existing file is unversioned but modified I will look at RemoveFile. It seems kind of counter intuitive that on installation I want to remove a file. Would I put the RemoveFile element in the same component as the component that is installing the file? -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
