That sounds like the correct part of the File Versioning rules. Read the
blog entry and really the "correct" way to update files installed by the
Windows Installer is to use the Windows Installer to update them. However,
since you are dealing with unversioned files your work around will probably
be
According to my understanding, I've tried to summarize all information and
the solution in our blog:
http://blog.syntevo.net/2009/11/08/125770902.html
If something is wrong, please let me know. Thanks in advance.
Tom
Thomas Singer wrote:
> Thanks for the hint to the File Versioning Rules:
Thanks for the hint to the File Versioning Rules:
http://msdn.microsoft.com/en-us/library/aa368599(VS.85).aspx
Do I understand it correctly, that file versions and languages solely apply
to .exe/.dll or similar files, but not to, for example, .jar files which are
nothing else than .zip files? Th
Take a look at the element. It will get rid of existing
files before the new files are copied in to place. Might help in this
situation.
Chad
-Original Message-
From: Thomas Singer [mailto:w...@regnis.de]
Sent: Wednesday, November 04, 2009 10:13 AM
To: wix-users@lists.sourceforge.net
Su
This isn't a WiX problem. It's MSI, and there's nothing you can really do
about it in the setup authoring, as far as I know. The only way I'm aware
of to change it is to use MSIEXEC command line parameters to tell MSI to
overwrite changed files.
You should really look into using patches or MS
5 matches
Mail list logo
