Hi!
Question 1)
Automation build with msbuild. We are using the version "1.0.*" in the
.Net assemblies we build and would like to keep this.
During the day the revision number is the only one changing as the build
number is used to represent the day. Now as the installer only uses the
three first number in version to separate different versions. How to
separate different build during the day so the installer understands it.
Someone has a similar build environment and have any suggestions how
configure the environment?
Question 2)
Was playing around with Upgrade. Now I have:
<Product Id="$(var.ProductId)" ...
<Upgrade
Id="6F148500-B37D-4a81-976E-9485ADEC4BA5">
<UpgradeVersion
Property="OLDAPPFOUND" IncludeMinimum="yes" Minimum="0.0.0.0"
IncludeMaximum="no" Maximum="$(var.ProductVersion)"/>
<UpgradeVersion
Property="NEWAPPFOUND" IncludeMinimum="no" Minimum
="$(var.ProductVersion)"
OnlyDetect="yes"/>
</Upgrade>
<InstallExecuteSequence>
<RemoveExistingProducts
After="InstallInitialize" />
</InstallExecuteSequence>
Now it seems to work if I have a new build number in the version, it
will reinstall files. (Why have revision number at all in the version
number?)
I had:
<RemoveExistingProducts After="InstallFinalize" />
And it didn't reinstall files. It kept files that had an old version on
them. Why?
/cj
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
