Anyone know how I can set a file version? I read through the links that Blair provided and I believe setting the file version of my new files is the best way to move forward.
My understanding is that I need to specify the file version in my new installers. This will: 1. Insure that the existing files with a hash but no version are upgraded 2. More importantly, insure that these upgraded files aren't overwritten when an older installer w/o file version info is run after the new installer. I could use the "DefaultVersion" attribute of the file element and use the suppress files option in "light", but this would suppress the file version of all files. It seems like the best way to move forward is to specifically set the file version of my updated files. Unfortunately, I can't figure out how to do that, which leads me to the question.... "Anyone know how I can set a file version? Thanks, Craig On Wed, Jun 30, 2010 at 2:08 PM, Blair <os...@live.com> wrote: > With regards to files that don't have Version resources (since WiX's binder > by default does populate the file hash for files that don't contain version > resources) the following pages are of use to help you understand what is > expected. > > The default behavior for your case is described on this page: > http://msdn.microsoft.com/library/aa370532.aspx > > REINSTALLMODE is described here: > http://msdn.microsoft.com/library/aa371182.aspx > > The default value for REINSTALLMODE is documented as "omus". > > Additional information about file replacement rules (versioning) covering > additional cases is found in the same area of the MSDN library. > > -----Original Message----- > From: Miller, Craig [mailto:craig.mil...@spatialminds.com] > Sent: Wednesday, June 30, 2010 11:55 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Component Level Versioning? > > Thanks Peter and Pally for the replies. > > I don't make a lot of installers, but I did read and follow the > component rules very carefully when I created the original installer. > What I'm unclear on is if I have the same component snippet in two MSI > files (same GUID), but one snippet contains a newer version of the > underlying file, how does the windows installer know that the newer > version is in fact a newer version? > > E.g. > Version 1 created in 2008 and Version 2 created in 2010 are identical > except the "Source" attribute of the "File" element points to an > updated version of the file "..\USGS > Topographic\250k\NY\c43078a1.tif". Since components don't appear to > have any version info, if I run the version 2 installer, followed by > the version 1 installer, what prevents the old file from overwriting > the newer file? > > <Component Id='c43078a1.tif' Guid='784351B6-50BC-43B3-B668-F5248B4A4B90'> > <File Id='c43078a1.tif' > Name='c43078a1.tif' DiskId='1' > KeyPath='yes' > Source='..\USGS Topographic\250k\NY\c43078a1.tif' /> > </Component> > > > Agreed, VMs are very helpful for this sort of thing. > > Craig > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Craig Miller Geospatial Software Architect ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
