SteveKing wrote:
> Russell Hind wrote:
>
>> Yep, I'll get it uploaded with the nightlies.
>>
>> Stefan,
>>
>> How many places is the GUID required? Would it be possible for my
>> build scrip to call a guidgen.exe program to output the guid to a
>> text file so the GUID changes every night or can't the installer
>> stuff pick it up from a file?
>
>
> The problem is: that depends. If we change something major in the
> installaton process or release a new version, then two GUIDs need to
> be changed. For simple updates only one has to be changed.
> And I don't know how to use the guidgen.exe in a simple way to write
> that GUID _in_ a file at a specific position, i.e. replacing the old
> one. The GUID is located inside an XML struct, so it's not possible to
> just grab one with an include statement from another file.
>
> Stefan
>
Having just spend a couple weeks working with WiX for my company's
product, here is my input:
*If* you wanted to change both everytime (which it sounds like you
don't), WiX supports ????????-????-????-????-???????????? in the
Package ID and Product ID fields. It will then generate a new GUID at
build time. However, it's not that simple, if you just change those
without changing the version number, the installer won't upgrade the
existing installer, it will just install another copy. If you adjust
the upgrade table to do upgrades when the current version is already
installed, then the maintenance dialog won't come up when someone reruns
the MSI for their current install.
My suggestion would be to use ????????-????-????-????-???????????? for
the package Id (since it really is supposed to change whenever a new MSI
is built anyway). Leave the version number and Product ID alone for
nightlies and only change them at release time. Then, it may be usually
(as long as new components don't get created and features don't change)
to "reinstall" with the nightly MSI without uninstalling by using a
command like this (which could be put in a reinstall.bat on the website
if desired):
msiexec /qb /i TortoiseSVN-1.1.x-UNICODE_svn-1.1.x.msi REINSTALL=ALL
REINSTALLMODE=vomus
Note, this sort of reinstall only replaces files with newer versions and
updates registry settings, etc. It does not typically work well if
components change or are reorganized. Note, I have not tried this sort
of reinstall with the tortoise MSI, but I can try it tomorrow.
All in all, upgrades are a pain :)
Erv
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Oct 21 21:47:42 2004