Can someone explain to me the rational behind the definition of a "small update"? My CM background has never liked the though of shipping a new MSI that had the same ProductVersion as a previous MSI. Even if the PackageCode GUID is different. It just doesn't make sense to me.
---------------------------------------- From: "David Watson" <dwat...@sdl.com> Sent: Tuesday, August 06, 2013 10:49 AM To: "General discussion for Windows Installer XML toolset." <wix-users@lists.sourceforge.net> Subject: Re: [WiX-users] Versioning on small updates You need to update the file version to allow windows installer to know whether or not to overwrite any existing file. http://msdn.microsoft.com/en-us/library/windows/desktop/aa368599(v=vs.85).asp x I don't think the string version is used but I always keep them both in sync anyway. Windows installer honours and recognises all four parts of file versions (you are correct that it only recognises the first 3 parts of msi product versions). -----Original Message----- From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com] Sent: 06 August 2013 06:42 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Versioning on small updates According to the MSDN documentation, small updates are for small fixes that don't change the product version. But I can't find definite information on what to do with *file* versions. Do I still need to increase the file version (in the VERSIONINFO resource) of Win32 PE files that I modify in a small update patch? If yes, is that the numeric FILEVERSION, the string FileVersion, or both? And can I bump only the 4th component, or does Windows Installer only take the first three into account? (Perhaps I'm mixing things up and that's only for MSI product versions, not file versions...) -- Nicolás ----------------------------------------------------------------------------- - Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
