ok, so I got it right: the 4th field is completely ignored by the
installer, and you have it so that internally the QA knows what version
they are testing.
Thx a lot!
Viv
On 4/13/2010 12:47 AM, Sascha Beaumont wrote:
> Because in our environment the fourth version is increased
> automatically w
Because in our environment the fourth version is increased
automatically with every build, how else would you differentiate from
the "old" v1.1.1 and the "new" v1.1.1 ??
On Mon, Apr 12, 2010 at 6:02 PM, Viv Coco wrote:
> Hi Sascha,
>
> Thank you for your answer.
> I understood your suggestion, b
Hi Sascha,
Thank you for your answer.
I understood your suggestion, but what it's not clear to me is why do
you actually have the 4th field in the version? I mean the approach you
have would have worked exactly the same also if your version number
would consist of only 3 fields, eg: 2.2.0, whic
You can't do this while also using Product/@Id="*", a product with the
same version but different ID is seen as a different package. The best
solution that I've come up with is to increase the fourth version
field and block installation when the version number is the same.
Windows Installer ignores
4 matches
Mail list logo
