Re: [WiX-users] MajorUpgrade element problems

2014-06-04 Thread Przemyslaw Galera 
Thank you guys...you are with me now :)
I can't change the released products, though.

What I have already tried is the MajorUpgrade with 
AllowSameVersionUpgrades="yes" and AllowDowngrades="no"...but there is still no 
way to preserve the old Upgrade Logic.

For my taste, this configuration would allow Downgrading between builds as 
well...  ---> could you please confirm or deny?  <---
Anyway I wouldn't say it would complain about the downgrade build number even 
while using MajorUpgrade element, while the Windows Installer doesn't care 
about it at all...only 3 fields are taken under consideration there.

Przemyslaw Galera
Software Engineer
IndigoVision
Tel: +44 (0) 131 475 7336 (x336)
Email: p.gal...@indigovision.com
www.indigovision.com
Complete IP Video Security Solutions


-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 04 June 2014 17:21
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems

There is one option, you can set AllowSameVersionUpgrades that will allow 
1.0.0.0 to be upgraded to 1.0.0.1 but (and it is a big but) it will also make 
1.0.0.1 upgrade to 1.0.0.0 which is dangerous.

But as Phil said, changing the version scheme is the safest option.

Neil

-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: 04 June 2014 17:12
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems

I'll repeat the part that says you can't do any kind of major upgrade unless 
you change your version in the first 3 fields. You cannot major upgrade from 
product version 2.0.0.1 to 2.0.0.5, which makes any use of majorupgrade or 
upgrade elements irrelevant. Remarks here:

http://msdn.microsoft.com/en-us/library/aa370859(v=vs.85).aspx


---
Phil Wilson


On Wed, Jun 4, 2014 at 8:56 AM, Przemyslaw Galera  
wrote:
> Thanks again!
> Can we say at this point, that MajorUpgrade and Upgrade elements cannot be 
> used within the same wxs file?
>
> I thought, I would be able to upgrade between builds just by forcing major 
> upgrade  ---> which will uninstall the previous Software version <---   for 
> each supported upgrade path. What is the problem with using the 
> UpgradeVersions for the Software I have?
>
> Thank you!
>
> Przemyslaw Galera
> Software Engineer
> IndigoVision
> Tel: +44 (0) 131 475 7336 (x336)
> Email: p.gal...@indigovision.com
> www.indigovision.com
> Complete IP Video Security Solutions
>
>
> -Original Message-
> From: Phil Wilson [mailto:phildgwil...@gmail.com]
> Sent: 04 June 2014 16:08
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] MajorUpgrade element problems
>
> Ok, but I think somebody may have already mentioned that you can't upgrade 
> from 2.0.0.1 to 2.0.0.5 because Windows Installer upgrades use only the first 
> 3 fields of the version.  You can't use upgrade elements or majorupgrade for 
> this reason. Manually uninstall or just change your new version to 2.0.1. 
> You've got to play by the rules because now you don't have a WiX issue or an 
> MSI issue - you have a problem created by your usage of product version that 
> you need to solve in some way that doesn't use major upgrades at all.
> ---
> Phil Wilson
>
>
> On Wed, Jun 4, 2014 at 7:53 AM, Przemyslaw Galera  
> wrote:
>> Hi,
>> Thanks for your help.
>>
>> I do realize that. I have several UpgradeVersions in my configuration file. 
>> The question was about the particular tricky versions:  --->  upgrade from 
>> 2.0.0.1 to 2.0.0.5 <---  , not the upgrade from 5.0.0 to 9.0.0...these are a 
>> normal upgrade versions handled very well.
>>
>>
>> " The solution with using a wild card as a Product/Id is not much helpful as 
>> it leaves me end up with the two Software versions installed side-by-side in 
>> the ControlPanel if I use versions  2.0.0.1 and 2.0.0.5. I know, that MSI 
>> does only care about the 3 version numbers, not about the 4th one."
>>
>> Przemyslaw Galera
>> Software Engineer
>> IndigoVision
>> Tel: +44 (0) 131 475 7336 (x336)
>> Email: p.gal...@indigovision.com
>> www.indigovision.com
>> Complete IP Video Security Solutions
>>
>> -Original Message-
>> From: Phil Wilson [mailto:phildgwil...@gmail.com]
>> Sent: 04 June 2014 15:20
>> To: General discussion about the WiX toolset.
>> Subject: Re: [WiX-users] MajorUpgrade element problems
>>
>> You may not realize that you can have multiple Upgrade elements. So you can 
>> forget the MajorUpgrade and do something like this, off the top of my head:
>>

Re: [WiX-users] MajorUpgrade element problems

2014-06-04 Thread Neil Sleightholm 
There is one option, you can set AllowSameVersionUpgrades that will allow 
1.0.0.0 to be upgraded to 1.0.0.1 but (and it is a big but) it will also make 
1.0.0.1 upgrade to 1.0.0.0 which is dangerous. 

But as Phil said, changing the version scheme is the safest option.

Neil

-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com] 
Sent: 04 June 2014 17:12
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems

I'll repeat the part that says you can't do any kind of major upgrade unless 
you change your version in the first 3 fields. You cannot major upgrade from 
product version 2.0.0.1 to 2.0.0.5, which makes any use of majorupgrade or 
upgrade elements irrelevant. Remarks here:

http://msdn.microsoft.com/en-us/library/aa370859(v=vs.85).aspx


---
Phil Wilson


On Wed, Jun 4, 2014 at 8:56 AM, Przemyslaw Galera  
wrote:
> Thanks again!
> Can we say at this point, that MajorUpgrade and Upgrade elements cannot be 
> used within the same wxs file?
>
> I thought, I would be able to upgrade between builds just by forcing major 
> upgrade  ---> which will uninstall the previous Software version <---   for 
> each supported upgrade path. What is the problem with using the 
> UpgradeVersions for the Software I have?
>
> Thank you!
>
> Przemyslaw Galera
> Software Engineer
> IndigoVision
> Tel: +44 (0) 131 475 7336 (x336)
> Email: p.gal...@indigovision.com
> www.indigovision.com
> Complete IP Video Security Solutions
>
>
> -Original Message-
> From: Phil Wilson [mailto:phildgwil...@gmail.com]
> Sent: 04 June 2014 16:08
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] MajorUpgrade element problems
>
> Ok, but I think somebody may have already mentioned that you can't upgrade 
> from 2.0.0.1 to 2.0.0.5 because Windows Installer upgrades use only the first 
> 3 fields of the version.  You can't use upgrade elements or majorupgrade for 
> this reason. Manually uninstall or just change your new version to 2.0.1. 
> You've got to play by the rules because now you don't have a WiX issue or an 
> MSI issue - you have a problem created by your usage of product version that 
> you need to solve in some way that doesn't use major upgrades at all.
> ---
> Phil Wilson
>
>
> On Wed, Jun 4, 2014 at 7:53 AM, Przemyslaw Galera  
> wrote:
>> Hi,
>> Thanks for your help.
>>
>> I do realize that. I have several UpgradeVersions in my configuration file. 
>> The question was about the particular tricky versions:  --->  upgrade from 
>> 2.0.0.1 to 2.0.0.5 <---  , not the upgrade from 5.0.0 to 9.0.0...these are a 
>> normal upgrade versions handled very well.
>>
>>
>> " The solution with using a wild card as a Product/Id is not much helpful as 
>> it leaves me end up with the two Software versions installed side-by-side in 
>> the ControlPanel if I use versions  2.0.0.1 and 2.0.0.5. I know, that MSI 
>> does only care about the 3 version numbers, not about the 4th one."
>>
>> Przemyslaw Galera
>> Software Engineer
>> IndigoVision
>> Tel: +44 (0) 131 475 7336 (x336)
>> Email: p.gal...@indigovision.com
>> www.indigovision.com
>> Complete IP Video Security Solutions
>>
>> -Original Message-
>> From: Phil Wilson [mailto:phildgwil...@gmail.com]
>> Sent: 04 June 2014 15:20
>> To: General discussion about the WiX toolset.
>> Subject: Re: [WiX-users] MajorUpgrade element problems
>>
>> You may not realize that you can have multiple Upgrade elements. So you can 
>> forget the MajorUpgrade and do something like this, off the top of my head:
>>
>>  > Id="7F4A46B0-A6E7-4EEA-8655-235BCA4AB2C4">
>>>   Minimum="5.0.0" Maximum="9.0.0"
>>   Property="PREVIOUSVERSIONSINSTALLED"
>>   IncludeMinimum="yes" IncludeMaximum="no" />  > Id="DISALLOWUP" Secure="yes" /> > Id="7F4A46B0-A6E7-4EEA-8655-235BCA4AB2C4">
>>>   Minimum="1.0.0" Maximum="8.0.0"
>>   Property="DISALLOWUP"
>>   IncludeMinimum="yes" IncludeMaximum="no" OnlyDetect="yes"/> 
>> 
>>
>> and add a RemoveExistingProducts to the InstallExecuteSequence.  This gives 
>> you an upgrade for versions 5 to 9 and a property DISALLOWUP that you can 
>> use to condition an error after the FindRelatedProducts action.
>> ---
>> Phil Wilson
>>
>>
>> On Wed, Jun 4, 2014 at 3:28 AM, Przemyslaw Galera 
>>

Re: [WiX-users] MajorUpgrade element problems

2014-06-04 Thread Phil Wilson 
I'll repeat the part that says you can't do any kind of major upgrade
unless you change your version in the first 3 fields. You cannot major
upgrade from product version 2.0.0.1 to 2.0.0.5, which makes any use
of majorupgrade or upgrade elements irrelevant. Remarks here:

http://msdn.microsoft.com/en-us/library/aa370859(v=vs.85).aspx


---
Phil Wilson


On Wed, Jun 4, 2014 at 8:56 AM, Przemyslaw Galera
 wrote:
> Thanks again!
> Can we say at this point, that MajorUpgrade and Upgrade elements cannot be 
> used within the same wxs file?
>
> I thought, I would be able to upgrade between builds just by forcing major 
> upgrade  ---> which will uninstall the previous Software version <---   for 
> each supported upgrade path. What is the problem with using the 
> UpgradeVersions for the Software I have?
>
> Thank you!
>
> Przemyslaw Galera
> Software Engineer
> IndigoVision
> Tel: +44 (0) 131 475 7336 (x336)
> Email: p.gal...@indigovision.com
> www.indigovision.com
> Complete IP Video Security Solutions
>
>
> -Original Message-
> From: Phil Wilson [mailto:phildgwil...@gmail.com]
> Sent: 04 June 2014 16:08
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] MajorUpgrade element problems
>
> Ok, but I think somebody may have already mentioned that you can't upgrade 
> from 2.0.0.1 to 2.0.0.5 because Windows Installer upgrades use only the first 
> 3 fields of the version.  You can't use upgrade elements or majorupgrade for 
> this reason. Manually uninstall or just change your new version to 2.0.1. 
> You've got to play by the rules because now you don't have a WiX issue or an 
> MSI issue - you have a problem created by your usage of product version that 
> you need to solve in some way that doesn't use major upgrades at all.
> ---
> Phil Wilson
>
>
> On Wed, Jun 4, 2014 at 7:53 AM, Przemyslaw Galera  
> wrote:
>> Hi,
>> Thanks for your help.
>>
>> I do realize that. I have several UpgradeVersions in my configuration file. 
>> The question was about the particular tricky versions:  --->  upgrade from 
>> 2.0.0.1 to 2.0.0.5 <---  , not the upgrade from 5.0.0 to 9.0.0...these are a 
>> normal upgrade versions handled very well.
>>
>>
>> " The solution with using a wild card as a Product/Id is not much helpful as 
>> it leaves me end up with the two Software versions installed side-by-side in 
>> the ControlPanel if I use versions  2.0.0.1 and 2.0.0.5. I know, that MSI 
>> does only care about the 3 version numbers, not about the 4th one."
>>
>> Przemyslaw Galera
>> Software Engineer
>> IndigoVision
>> Tel: +44 (0) 131 475 7336 (x336)
>> Email: p.gal...@indigovision.com
>> www.indigovision.com
>> Complete IP Video Security Solutions
>>
>> -Original Message-
>> From: Phil Wilson [mailto:phildgwil...@gmail.com]
>> Sent: 04 June 2014 15:20
>> To: General discussion about the WiX toolset.
>> Subject: Re: [WiX-users] MajorUpgrade element problems
>>
>> You may not realize that you can have multiple Upgrade elements. So you can 
>> forget the MajorUpgrade and do something like this, off the top of my head:
>>
>>  > Id="7F4A46B0-A6E7-4EEA-8655-235BCA4AB2C4">
>>>   Minimum="5.0.0" Maximum="9.0.0"
>>   Property="PREVIOUSVERSIONSINSTALLED"
>>   IncludeMinimum="yes" IncludeMaximum="no" />  > Id="DISALLOWUP" Secure="yes" /> > Id="7F4A46B0-A6E7-4EEA-8655-235BCA4AB2C4">
>>>   Minimum="1.0.0" Maximum="8.0.0"
>>   Property="DISALLOWUP"
>>   IncludeMinimum="yes" IncludeMaximum="no" OnlyDetect="yes"/>
>> 
>>
>> and add a RemoveExistingProducts to the InstallExecuteSequence.  This gives 
>> you an upgrade for versions 5 to 9 and a property DISALLOWUP that you can 
>> use to condition an error after the FindRelatedProducts action.
>> ---
>> Phil Wilson
>>
>>
>> On Wed, Jun 4, 2014 at 3:28 AM, Przemyslaw Galera 
>>  wrote:
>>> Hi,
>>> Thank you for the answer.
>>> This is exactly how it is set right now. The point is, I wanted to force 
>>> the Major Upgrade for all the supported Software upgrades, but not for all.
>>>
>>> Is there any way to use Upgrade/UpgradeVersion and MajorUpgrade elements 
>>> next to each other within the Product? I have tried that, and it doesn't 
>>> work, because of the same Id's for

Re: [WiX-users] MajorUpgrade element problems

2014-06-04 Thread Przemyslaw Galera 
Thanks again!
Can we say at this point, that MajorUpgrade and Upgrade elements cannot be used 
within the same wxs file?

I thought, I would be able to upgrade between builds just by forcing major 
upgrade  ---> which will uninstall the previous Software version <---   for 
each supported upgrade path. What is the problem with using the UpgradeVersions 
for the Software I have?

Thank you!

Przemyslaw Galera
Software Engineer
IndigoVision
Tel: +44 (0) 131 475 7336 (x336)
Email: p.gal...@indigovision.com
www.indigovision.com
Complete IP Video Security Solutions


-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: 04 June 2014 16:08
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems

Ok, but I think somebody may have already mentioned that you can't upgrade from 
2.0.0.1 to 2.0.0.5 because Windows Installer upgrades use only the first 3 
fields of the version.  You can't use upgrade elements or majorupgrade for this 
reason. Manually uninstall or just change your new version to 2.0.1. You've got 
to play by the rules because now you don't have a WiX issue or an MSI issue - 
you have a problem created by your usage of product version that you need to 
solve in some way that doesn't use major upgrades at all.
---
Phil Wilson


On Wed, Jun 4, 2014 at 7:53 AM, Przemyslaw Galera  
wrote:
> Hi,
> Thanks for your help.
>
> I do realize that. I have several UpgradeVersions in my configuration file. 
> The question was about the particular tricky versions:  --->  upgrade from 
> 2.0.0.1 to 2.0.0.5 <---  , not the upgrade from 5.0.0 to 9.0.0...these are a 
> normal upgrade versions handled very well.
>
>
> " The solution with using a wild card as a Product/Id is not much helpful as 
> it leaves me end up with the two Software versions installed side-by-side in 
> the ControlPanel if I use versions  2.0.0.1 and 2.0.0.5. I know, that MSI 
> does only care about the 3 version numbers, not about the 4th one."
>
> Przemyslaw Galera
> Software Engineer
> IndigoVision
> Tel: +44 (0) 131 475 7336 (x336)
> Email: p.gal...@indigovision.com
> www.indigovision.com
> Complete IP Video Security Solutions
>
> -Original Message-
> From: Phil Wilson [mailto:phildgwil...@gmail.com]
> Sent: 04 June 2014 15:20
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] MajorUpgrade element problems
>
> You may not realize that you can have multiple Upgrade elements. So you can 
> forget the MajorUpgrade and do something like this, off the top of my head:
>
>   Id="7F4A46B0-A6E7-4EEA-8655-235BCA4AB2C4">
>   Minimum="5.0.0" Maximum="9.0.0"
>   Property="PREVIOUSVERSIONSINSTALLED"
>   IncludeMinimum="yes" IncludeMaximum="no" />   Id="DISALLOWUP" Secure="yes" />  Id="7F4A46B0-A6E7-4EEA-8655-235BCA4AB2C4">
>   Minimum="1.0.0" Maximum="8.0.0"
>   Property="DISALLOWUP"
>   IncludeMinimum="yes" IncludeMaximum="no" OnlyDetect="yes"/>
> 
>
> and add a RemoveExistingProducts to the InstallExecuteSequence.  This gives 
> you an upgrade for versions 5 to 9 and a property DISALLOWUP that you can use 
> to condition an error after the FindRelatedProducts action.
> ---
> Phil Wilson
>
>
> On Wed, Jun 4, 2014 at 3:28 AM, Przemyslaw Galera  
> wrote:
>> Hi,
>> Thank you for the answer.
>> This is exactly how it is set right now. The point is, I wanted to force the 
>> Major Upgrade for all the supported Software upgrades, but not for all.
>>
>> Is there any way to use Upgrade/UpgradeVersion and MajorUpgrade elements 
>> next to each other within the Product? I have tried that, and it doesn't 
>> work, because of the same Id's for Upgrade and MajorUpgrade.
>>
>> The solution with using a wild card as a Product/Id is not much helpful as 
>> it leaves me end up with the two Software versions installed side-by-side in 
>> the ControlPanel if I use versions  2.0.0.1 and 2.0.0.5. I know, that MSI 
>> does only care about the 3 version numbers, not about the 4th one.
>>
>> Thank you in advance!
>>
>> Kindest regards,
>> Przemyslaw Galera
>> Software Engineer
>> IndigoVision
>> Tel: +44 (0) 131 475 7336 (x336)
>> Email: p.gal...@indigovision.com
>> www.indigovision.com
>> Complete IP Video Security Solutions
>>
>>
>> -Original Message-
>> From: David Watson [mailto:dwat...@sdl.com]
>> Sent: 04 June 2014 10:39
>> To: General discussion about the WiX toolset.

Re: [WiX-users] MajorUpgrade element problems

2014-06-04 Thread Phil Wilson 
Ok, but I think somebody may have already mentioned that you can't
upgrade from 2.0.0.1 to 2.0.0.5 because Windows Installer upgrades use
only the first 3 fields of the version.  You can't use upgrade
elements or majorupgrade for this reason. Manually uninstall or just
change your new version to 2.0.1. You've got to play by the rules
because now you don't have a WiX issue or an MSI issue - you have a
problem created by your usage of product version that you need to
solve in some way that doesn't use major upgrades at all.
---
Phil Wilson


On Wed, Jun 4, 2014 at 7:53 AM, Przemyslaw Galera
 wrote:
> Hi,
> Thanks for your help.
>
> I do realize that. I have several UpgradeVersions in my configuration file. 
> The question was about the particular tricky versions:  --->  upgrade from 
> 2.0.0.1 to 2.0.0.5 <---  , not the upgrade from 5.0.0 to 9.0.0...these are a 
> normal upgrade versions handled very well.
>
>
> " The solution with using a wild card as a Product/Id is not much helpful as 
> it leaves me end up with the two Software versions installed side-by-side in 
> the ControlPanel if I use versions  2.0.0.1 and 2.0.0.5. I know, that MSI 
> does only care about the 3 version numbers, not about the 4th one."
>
> Przemyslaw Galera
> Software Engineer
> IndigoVision
> Tel: +44 (0) 131 475 7336 (x336)
> Email: p.gal...@indigovision.com
> www.indigovision.com
> Complete IP Video Security Solutions
>
> -Original Message-
> From: Phil Wilson [mailto:phildgwil...@gmail.com]
> Sent: 04 June 2014 15:20
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] MajorUpgrade element problems
>
> You may not realize that you can have multiple Upgrade elements. So you can 
> forget the MajorUpgrade and do something like this, off the top of my head:
>
>   Id="7F4A46B0-A6E7-4EEA-8655-235BCA4AB2C4">
>   Minimum="5.0.0" Maximum="9.0.0"
>   Property="PREVIOUSVERSIONSINSTALLED"
>   IncludeMinimum="yes" IncludeMaximum="no" />   Id="DISALLOWUP" Secure="yes" />  Id="7F4A46B0-A6E7-4EEA-8655-235BCA4AB2C4">
>   Minimum="1.0.0" Maximum="8.0.0"
>   Property="DISALLOWUP"
>   IncludeMinimum="yes" IncludeMaximum="no" OnlyDetect="yes"/> 
>
> and add a RemoveExistingProducts to the InstallExecuteSequence.  This gives 
> you an upgrade for versions 5 to 9 and a property DISALLOWUP that you can use 
> to condition an error after the FindRelatedProducts action.
> ---
> Phil Wilson
>
>
> On Wed, Jun 4, 2014 at 3:28 AM, Przemyslaw Galera  
> wrote:
>> Hi,
>> Thank you for the answer.
>> This is exactly how it is set right now. The point is, I wanted to force the 
>> Major Upgrade for all the supported Software upgrades, but not for all.
>>
>> Is there any way to use Upgrade/UpgradeVersion and MajorUpgrade elements 
>> next to each other within the Product? I have tried that, and it doesn't 
>> work, because of the same Id's for Upgrade and MajorUpgrade.
>>
>> The solution with using a wild card as a Product/Id is not much helpful as 
>> it leaves me end up with the two Software versions installed side-by-side in 
>> the ControlPanel if I use versions  2.0.0.1 and 2.0.0.5. I know, that MSI 
>> does only care about the 3 version numbers, not about the 4th one.
>>
>> Thank you in advance!
>>
>> Kindest regards,
>> Przemyslaw Galera
>> Software Engineer
>> IndigoVision
>> Tel: +44 (0) 131 475 7336 (x336)
>> Email: p.gal...@indigovision.com
>> www.indigovision.com
>> Complete IP Video Security Solutions
>>
>>
>> -Original Message-
>> From: David Watson [mailto:dwat...@sdl.com]
>> Sent: 04 June 2014 10:39
>> To: General discussion about the WiX toolset.
>> Subject: Re: [WiX-users] MajorUpgrade element problems
>>
>> If you want to block the installation you can use the upgradeVersion element 
>> with OnlyDetect='yes' to set a property to use in a launch condition with 
>> your error message.
>>
>> If you want to break the new installation away from the previous versions 
>> and allow for side by side installation you can change the upgrade guid.
>>
>> -Original Message-
>> From: Przemyslaw Galera [mailto:p.gal...@indigovision.com]
>> Sent: 04 June 2014 10:02
>> To: General discussion about the WiX toolset.
>> Subject: Re: [WiX-users] MajorUpgrade element problems
>>
>> Hello,
>> Thank you very much for

Re: [WiX-users] MajorUpgrade element problems

2014-06-04 Thread Przemyslaw Galera 
Hi,
Thanks for your help.

I do realize that. I have several UpgradeVersions in my configuration file. The 
question was about the particular tricky versions:  --->  upgrade from 2.0.0.1 
to 2.0.0.5 <---  , not the upgrade from 5.0.0 to 9.0.0...these are a normal 
upgrade versions handled very well.


" The solution with using a wild card as a Product/Id is not much helpful as it 
leaves me end up with the two Software versions installed side-by-side in the 
ControlPanel if I use versions  2.0.0.1 and 2.0.0.5. I know, that MSI does only 
care about the 3 version numbers, not about the 4th one."

Przemyslaw Galera
Software Engineer
IndigoVision 
Tel: +44 (0) 131 475 7336 (x336)
Email: p.gal...@indigovision.com
www.indigovision.com
Complete IP Video Security Solutions

-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com] 
Sent: 04 June 2014 15:20
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems

You may not realize that you can have multiple Upgrade elements. So you can 
forget the MajorUpgrade and do something like this, off the top of my head:

 
  


and add a RemoveExistingProducts to the InstallExecuteSequence.  This gives you 
an upgrade for versions 5 to 9 and a property DISALLOWUP that you can use to 
condition an error after the FindRelatedProducts action.
---
Phil Wilson


On Wed, Jun 4, 2014 at 3:28 AM, Przemyslaw Galera  
wrote:
> Hi,
> Thank you for the answer.
> This is exactly how it is set right now. The point is, I wanted to force the 
> Major Upgrade for all the supported Software upgrades, but not for all.
>
> Is there any way to use Upgrade/UpgradeVersion and MajorUpgrade elements next 
> to each other within the Product? I have tried that, and it doesn't work, 
> because of the same Id's for Upgrade and MajorUpgrade.
>
> The solution with using a wild card as a Product/Id is not much helpful as it 
> leaves me end up with the two Software versions installed side-by-side in the 
> ControlPanel if I use versions  2.0.0.1 and 2.0.0.5. I know, that MSI does 
> only care about the 3 version numbers, not about the 4th one.
>
> Thank you in advance!
>
> Kindest regards,
> Przemyslaw Galera
> Software Engineer
> IndigoVision
> Tel: +44 (0) 131 475 7336 (x336)
> Email: p.gal...@indigovision.com
> www.indigovision.com
> Complete IP Video Security Solutions
>
>
> -Original Message-
> From: David Watson [mailto:dwat...@sdl.com]
> Sent: 04 June 2014 10:39
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] MajorUpgrade element problems
>
> If you want to block the installation you can use the upgradeVersion element 
> with OnlyDetect='yes' to set a property to use in a launch condition with 
> your error message.
>
> If you want to break the new installation away from the previous versions and 
> allow for side by side installation you can change the upgrade guid.
>
> -Original Message-----
> From: Przemyslaw Galera [mailto:p.gal...@indigovision.com]
> Sent: 04 June 2014 10:02
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] MajorUpgrade element problems
>
> Hello,
> Thank you very much for your response.
>
> What hasn't been asked explicitly is: Can I use a MajorUpgrade element and 
> prevent the Software from upgrading from particular versions, that are not 
> supported?
>
> For example; I don't want to allow upgrades from versions prior to  2.1.0.0?
>
> Kindest regards,
>
> Przemyslaw Galera
> Software Engineer
> IndigoVision
> Tel: +44 (0) 131 475 7336 (x336)
> Email: p.gal...@indigovision.com
> www.indigovision.com
> Complete IP Video Security Solutions
>
>
> -Original Message-
> From: Jeremiahf [mailto:jeremi...@gmail.com]
> Sent: 02 June 2014 21:15
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] MajorUpgrade element problems
>
> FYI there is not an attachment.
>
> This is how I used to do it before my requirements changed...
>
> will upgrade 1.1.1.1 to 1.1.2.1 and not allow a downgrade.
>
> keep the Upgradecode static and the product/Package Ids to "*"
>
> I use a config.wxi file that I include into product.wxs then reference the 
> values with variables.
>
> Up to you how to implement the values though...
>
> Example:
>
> 
>OnlyDetect="no" Property="NEWERVERSIONDETECTED"/>
>Maximum="$(var.InstallerProductVersion)" OnlyDetect="no"
> IncludeMinimum="yes" IncludeMaximum="no"
>   Property="OLDVERSIONBEINGUPGRADED" />
> 
>
> NOT NEWERVERSIONDETECTED
>
>

Re: [WiX-users] MajorUpgrade element problems

2014-06-04 Thread Phil Wilson 
You may not realize that you can have multiple Upgrade elements. So
you can forget the MajorUpgrade and do something like this, off the
top of my head:



   



   


and add a RemoveExistingProducts to the InstallExecuteSequence.  This
gives you an upgrade for versions 5 to 9 and a property DISALLOWUP
that you can use to condition an error after the FindRelatedProducts
action.
---
Phil Wilson


On Wed, Jun 4, 2014 at 3:28 AM, Przemyslaw Galera
 wrote:
> Hi,
> Thank you for the answer.
> This is exactly how it is set right now. The point is, I wanted to force the 
> Major Upgrade for all the supported Software upgrades, but not for all.
>
> Is there any way to use Upgrade/UpgradeVersion and MajorUpgrade elements next 
> to each other within the Product? I have tried that, and it doesn't work, 
> because of the same Id's for Upgrade and MajorUpgrade.
>
> The solution with using a wild card as a Product/Id is not much helpful as it 
> leaves me end up with the two Software versions installed side-by-side in the 
> ControlPanel if I use versions  2.0.0.1 and 2.0.0.5. I know, that MSI does 
> only care about the 3 version numbers, not about the 4th one.
>
> Thank you in advance!
>
> Kindest regards,
> Przemyslaw Galera
> Software Engineer
> IndigoVision
> Tel: +44 (0) 131 475 7336 (x336)
> Email: p.gal...@indigovision.com
> www.indigovision.com
> Complete IP Video Security Solutions
>
>
> -Original Message-
> From: David Watson [mailto:dwat...@sdl.com]
> Sent: 04 June 2014 10:39
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] MajorUpgrade element problems
>
> If you want to block the installation you can use the upgradeVersion element 
> with OnlyDetect='yes' to set a property to use in a launch condition with 
> your error message.
>
> If you want to break the new installation away from the previous versions and 
> allow for side by side installation you can change the upgrade guid.
>
> -Original Message-
> From: Przemyslaw Galera [mailto:p.gal...@indigovision.com]
> Sent: 04 June 2014 10:02
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] MajorUpgrade element problems
>
> Hello,
> Thank you very much for your response.
>
> What hasn't been asked explicitly is: Can I use a MajorUpgrade element and 
> prevent the Software from upgrading from particular versions, that are not 
> supported?
>
> For example; I don't want to allow upgrades from versions prior to  2.1.0.0?
>
> Kindest regards,
>
> Przemyslaw Galera
> Software Engineer
> IndigoVision
> Tel: +44 (0) 131 475 7336 (x336)
> Email: p.gal...@indigovision.com
> www.indigovision.com
> Complete IP Video Security Solutions
>
>
> -Original Message-
> From: Jeremiahf [mailto:jeremi...@gmail.com]
> Sent: 02 June 2014 21:15
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] MajorUpgrade element problems
>
> FYI there is not an attachment.
>
> This is how I used to do it before my requirements changed...
>
> will upgrade 1.1.1.1 to 1.1.2.1 and not allow a downgrade.
>
> keep the Upgradecode static and the product/Package Ids to "*"
>
> I use a config.wxi file that I include into product.wxs then reference the 
> values with variables.
>
> Up to you how to implement the values though...
>
> Example:
>
> 
>OnlyDetect="no" Property="NEWERVERSIONDETECTED"/>
>Maximum="$(var.InstallerProductVersion)" OnlyDetect="no"
> IncludeMinimum="yes" IncludeMaximum="no"
>   Property="OLDVERSIONBEINGUPGRADED" />
> 
>
> NOT NEWERVERSIONDETECTED
>
> 
>   
>   
> sequence>...
> 
>
> In order to meet version control by the 4th version number you would have to 
> use this (It is NOT a good practice.)
>
> There are other threads explaining why in detail. You should also research 
> how Microsoft handles version control to get more info in detail.
>
> This allows 1.1.1.1 to upgrade to 1.1.1.2 and not downgrade to 1.1.0.1 or 
> 1.1.0.2. Pretty much what you are seeing in a sense.
> 
>
>
> 
>   
>   
>
>
> Thank you,
>
> J
>
>
>
> On Mon, Jun 2, 2014 at 10:06 AM, Przemyslaw Galera < 
> p.gal...@indigovision.com> wrote:
>
>> Hi there!
>> I have a terrible problem with using the MajorUpgrade element in the
>> current installer we have. We tended to use the Upgrade element having
>> different error messages for different versions by using
>> UpgradeVersion property.
>> W

[WiX-users] MajorUpgrade element problems

2014-06-04 Thread Dharma.T.Gogineni 
I am new 2 wix.
I tried using burn but it is not generating the wixobj file. Below is the 
bundle I am trying to create. Is there anything wrong in this. I already have 
my two .msi's in sourcefile path. In the upgrade code I created a new GUID.


http://schemas.microsoft.com/wix/2006/wi";>

  http://wixtoolset.org";>



  
  

   



Am I missing anything?
Any help is appreciated.

--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their 
applications. Written by three acclaimed leaders in the field, 
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] MajorUpgrade element problems

2014-06-04 Thread Przemyslaw Galera 
Hi,
Thank you for the answer.
This is exactly how it is set right now. The point is, I wanted to force the 
Major Upgrade for all the supported Software upgrades, but not for all.

Is there any way to use Upgrade/UpgradeVersion and MajorUpgrade elements next 
to each other within the Product? I have tried that, and it doesn't work, 
because of the same Id's for Upgrade and MajorUpgrade.

The solution with using a wild card as a Product/Id is not much helpful as it 
leaves me end up with the two Software versions installed side-by-side in the 
ControlPanel if I use versions  2.0.0.1 and 2.0.0.5. I know, that MSI does only 
care about the 3 version numbers, not about the 4th one. 

Thank you in advance!

Kindest regards,
Przemyslaw Galera
Software Engineer
IndigoVision 
Tel: +44 (0) 131 475 7336 (x336)
Email: p.gal...@indigovision.com
www.indigovision.com
Complete IP Video Security Solutions


-Original Message-
From: David Watson [mailto:dwat...@sdl.com] 
Sent: 04 June 2014 10:39
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems

If you want to block the installation you can use the upgradeVersion element 
with OnlyDetect='yes' to set a property to use in a launch condition with your 
error message.

If you want to break the new installation away from the previous versions and 
allow for side by side installation you can change the upgrade guid. 

-Original Message-
From: Przemyslaw Galera [mailto:p.gal...@indigovision.com] 
Sent: 04 June 2014 10:02
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems

Hello,
Thank you very much for your response.

What hasn't been asked explicitly is: Can I use a MajorUpgrade element and 
prevent the Software from upgrading from particular versions, that are not 
supported?

For example; I don't want to allow upgrades from versions prior to  2.1.0.0? 

Kindest regards,

Przemyslaw Galera
Software Engineer
IndigoVision 
Tel: +44 (0) 131 475 7336 (x336)
Email: p.gal...@indigovision.com
www.indigovision.com
Complete IP Video Security Solutions


-Original Message-
From: Jeremiahf [mailto:jeremi...@gmail.com] 
Sent: 02 June 2014 21:15
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems

FYI there is not an attachment.

This is how I used to do it before my requirements changed...

will upgrade 1.1.1.1 to 1.1.2.1 and not allow a downgrade.

keep the Upgradecode static and the product/Package Ids to "*"

I use a config.wxi file that I include into product.wxs then reference the 
values with variables.

Up to you how to implement the values though...

Example:


  
  


NOT 
NEWERVERSIONDETECTED


  
  
   ...


In order to meet version control by the 4th version number you would have to 
use this (It is NOT a good practice.)

There are other threads explaining why in detail. You should also research how 
Microsoft handles version control to get more info in detail.

This allows 1.1.1.1 to upgrade to 1.1.1.2 and not downgrade to 1.1.0.1 or 
1.1.0.2. Pretty much what you are seeing in a sense.




  
  


Thank you,

J



On Mon, Jun 2, 2014 at 10:06 AM, Przemyslaw Galera < p.gal...@indigovision.com> 
wrote:

> Hi there!
> I have a terrible problem with using the MajorUpgrade element in the 
> current installer we have. We tended to use the Upgrade element having 
> different error messages for different versions by using 
> UpgradeVersion property.
> We wanted this behaviour to persist and to force the Major upgrade for 
> all the software upgrades. (Changing the Product.Id by using a 
> wildcard and using old UpgradeVersion is not the solution as it makes 
> the installer downgrading between builds with no errors - from 2.3.4.6 
> to 2.3.4.2 , having two software versions installed side-by-side).
>
>
> MajorUpgrade:
> ---
> It is not possible to specify the Minimum or Maximum upgradable 
> software version for this element, because the UpgradeVersion is not 
> supported by MajorUpgrade element, which prevents from creating the 
> custom actions with different error codes for particular software versions.
> ---
> Trying to work it around:
>
> Using the MajorUpgrade element side by side with Upgrade element is 
> not possible, as the MajorUpgrade's default Id is set to 
> Product.UpgradeCode which clashes with Upgrade.Id being set the same.
> There are error messages attached to the email.
>
> Could you please help? :)
>
> Thanks!
> Przemyslaw Galera
> Software Engineer
> IndigoVision
> Tel: +44 (0) 131 475 7336 (x336)
> Email: p.gal...@indigovision.com<mailto:p.gal...@indigovision.com>
> www.indigovision.com<http:

Re: [WiX-users] MajorUpgrade element problems

2014-06-04 Thread Neil Sleightholm 
The MajorUgrade element is a shortcut for the general cases, if you need 
something specific you either replace it with Upgrade elements or add Upgrade 
elements. In this case I would add a detect only Upgrade element.

Neil

-Original Message-
From: Przemyslaw Galera [mailto:p.gal...@indigovision.com] 
Sent: 04 June 2014 10:02
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems

Hello,
Thank you very much for your response.

What hasn't been asked explicitly is: Can I use a MajorUpgrade element and 
prevent the Software from upgrading from particular versions, that are not 
supported?

For example; I don't want to allow upgrades from versions prior to  2.1.0.0? 

Kindest regards,

Przemyslaw Galera
Software Engineer
IndigoVision 
Tel: +44 (0) 131 475 7336 (x336)
Email: p.gal...@indigovision.com
www.indigovision.com
Complete IP Video Security Solutions


-Original Message-
From: Jeremiahf [mailto:jeremi...@gmail.com] 
Sent: 02 June 2014 21:15
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems

FYI there is not an attachment.

This is how I used to do it before my requirements changed...

will upgrade 1.1.1.1 to 1.1.2.1 and not allow a downgrade.

keep the Upgradecode static and the product/Package Ids to "*"

I use a config.wxi file that I include into product.wxs then reference the 
values with variables.

Up to you how to implement the values though...

Example:


  
  


NOT 
NEWERVERSIONDETECTED


  
  
   ...


In order to meet version control by the 4th version number you would have to 
use this (It is NOT a good practice.)

There are other threads explaining why in detail. You should also research how 
Microsoft handles version control to get more info in detail.

This allows 1.1.1.1 to upgrade to 1.1.1.2 and not downgrade to 1.1.0.1 or 
1.1.0.2. Pretty much what you are seeing in a sense.




  
  


Thank you,

J



On Mon, Jun 2, 2014 at 10:06 AM, Przemyslaw Galera < p.gal...@indigovision.com> 
wrote:

> Hi there!
> I have a terrible problem with using the MajorUpgrade element in the 
> current installer we have. We tended to use the Upgrade element having 
> different error messages for different versions by using 
> UpgradeVersion property.
> We wanted this behaviour to persist and to force the Major upgrade for 
> all the software upgrades. (Changing the Product.Id by using a 
> wildcard and using old UpgradeVersion is not the solution as it makes 
> the installer downgrading between builds with no errors - from 2.3.4.6 
> to 2.3.4.2 , having two software versions installed side-by-side).
>
>
> MajorUpgrade:
> ---
> It is not possible to specify the Minimum or Maximum upgradable 
> software version for this element, because the UpgradeVersion is not 
> supported by MajorUpgrade element, which prevents from creating the 
> custom actions with different error codes for particular software versions.
> ---
> Trying to work it around:
>
> Using the MajorUpgrade element side by side with Upgrade element is 
> not possible, as the MajorUpgrade's default Id is set to 
> Product.UpgradeCode which clashes with Upgrade.Id being set the same.
> There are error messages attached to the email.
>
> Could you please help? :)
>
> Thanks!
> Przemyslaw Galera
> Software Engineer
> IndigoVision
> Tel: +44 (0) 131 475 7336 (x336)
> Email: p.gal...@indigovision.com<mailto:p.gal...@indigovision.com>
> www.indigovision.com<http://www.indigovision.com/>
> Complete IP Video Security Solutions
>
>
>
> --
>  Learn Graph Databases - Download FREE O'Reilly Book "Graph 
> Databases" is the definitive new guide to graph databases and their 
> applications. Written by three acclaimed leaders in the field, this 
> first edition is now available. Download your free book today!
> http://p.sf.net/sfu/NeoTech
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


--
"They may forget what you said but they will never forget how you made them 
feel." -- Anonymous
--
Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the 
definitive new guide to graph databases and their applications. Written by 
three acclaimed leaders in the field, this first edition is now available. 
Download your free book today!
http://p.sf.net/sfu/NeoTech

Re: [WiX-users] MajorUpgrade element problems

2014-06-04 Thread David Watson 
If you want to block the installation you can use the upgradeVersion element 
with OnlyDetect='yes' to set a property to use in a launch condition with your 
error message.

If you want to break the new installation away from the previous versions and 
allow for side by side installation you can change the upgrade guid. 

-Original Message-
From: Przemyslaw Galera [mailto:p.gal...@indigovision.com] 
Sent: 04 June 2014 10:02
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems

Hello,
Thank you very much for your response.

What hasn't been asked explicitly is: Can I use a MajorUpgrade element and 
prevent the Software from upgrading from particular versions, that are not 
supported?

For example; I don't want to allow upgrades from versions prior to  2.1.0.0? 

Kindest regards,

Przemyslaw Galera
Software Engineer
IndigoVision 
Tel: +44 (0) 131 475 7336 (x336)
Email: p.gal...@indigovision.com
www.indigovision.com
Complete IP Video Security Solutions


-Original Message-
From: Jeremiahf [mailto:jeremi...@gmail.com] 
Sent: 02 June 2014 21:15
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems

FYI there is not an attachment.

This is how I used to do it before my requirements changed...

will upgrade 1.1.1.1 to 1.1.2.1 and not allow a downgrade.

keep the Upgradecode static and the product/Package Ids to "*"

I use a config.wxi file that I include into product.wxs then reference the 
values with variables.

Up to you how to implement the values though...

Example:


  
  


NOT 
NEWERVERSIONDETECTED


  
  
   ...


In order to meet version control by the 4th version number you would have to 
use this (It is NOT a good practice.)

There are other threads explaining why in detail. You should also research how 
Microsoft handles version control to get more info in detail.

This allows 1.1.1.1 to upgrade to 1.1.1.2 and not downgrade to 1.1.0.1 or 
1.1.0.2. Pretty much what you are seeing in a sense.




  
  


Thank you,

J



On Mon, Jun 2, 2014 at 10:06 AM, Przemyslaw Galera < p.gal...@indigovision.com> 
wrote:

> Hi there!
> I have a terrible problem with using the MajorUpgrade element in the 
> current installer we have. We tended to use the Upgrade element having 
> different error messages for different versions by using 
> UpgradeVersion property.
> We wanted this behaviour to persist and to force the Major upgrade for 
> all the software upgrades. (Changing the Product.Id by using a 
> wildcard and using old UpgradeVersion is not the solution as it makes 
> the installer downgrading between builds with no errors - from 2.3.4.6 
> to 2.3.4.2 , having two software versions installed side-by-side).
>
>
> MajorUpgrade:
> ---
> It is not possible to specify the Minimum or Maximum upgradable 
> software version for this element, because the UpgradeVersion is not 
> supported by MajorUpgrade element, which prevents from creating the 
> custom actions with different error codes for particular software versions.
> ---
> Trying to work it around:
>
> Using the MajorUpgrade element side by side with Upgrade element is 
> not possible, as the MajorUpgrade's default Id is set to 
> Product.UpgradeCode which clashes with Upgrade.Id being set the same.
> There are error messages attached to the email.
>
> Could you please help? :)
>
> Thanks!
> Przemyslaw Galera
> Software Engineer
> IndigoVision
> Tel: +44 (0) 131 475 7336 (x336)
> Email: p.gal...@indigovision.com<mailto:p.gal...@indigovision.com>
> www.indigovision.com<http://www.indigovision.com/>
> Complete IP Video Security Solutions
>
>
>
> --
>  Learn Graph Databases - Download FREE O'Reilly Book "Graph 
> Databases" is the definitive new guide to graph databases and their 
> applications. Written by three acclaimed leaders in the field, this 
> first edition is now available. Download your free book today!
> http://p.sf.net/sfu/NeoTech
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


--
"They may forget what you said but they will never forget how you made them 
feel." -- Anonymous
--
Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the 
definitive new guide to graph databases and their applications. Written by 
three acclaimed leaders in the field, this fir

Re: [WiX-users] MajorUpgrade element problems

2014-06-04 Thread Przemyslaw Galera 
Hello,
Thank you very much for your response.

What hasn't been asked explicitly is: Can I use a MajorUpgrade element and 
prevent the Software from upgrading from particular versions, that are not 
supported?

For example; I don't want to allow upgrades from versions prior to  2.1.0.0? 

Kindest regards,

Przemyslaw Galera
Software Engineer
IndigoVision 
Tel: +44 (0) 131 475 7336 (x336)
Email: p.gal...@indigovision.com
www.indigovision.com
Complete IP Video Security Solutions


-Original Message-
From: Jeremiahf [mailto:jeremi...@gmail.com] 
Sent: 02 June 2014 21:15
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems

FYI there is not an attachment.

This is how I used to do it before my requirements changed...

will upgrade 1.1.1.1 to 1.1.2.1 and not allow a downgrade.

keep the Upgradecode static and the product/Package Ids to "*"

I use a config.wxi file that I include into product.wxs then reference the 
values with variables.

Up to you how to implement the values though...

Example:


  
  


NOT 
NEWERVERSIONDETECTED


  
  
   ...


In order to meet version control by the 4th version number you would have to 
use this (It is NOT a good practice.)

There are other threads explaining why in detail. You should also research how 
Microsoft handles version control to get more info in detail.

This allows 1.1.1.1 to upgrade to 1.1.1.2 and not downgrade to 1.1.0.1 or 
1.1.0.2. Pretty much what you are seeing in a sense.




  
  


Thank you,

J



On Mon, Jun 2, 2014 at 10:06 AM, Przemyslaw Galera < p.gal...@indigovision.com> 
wrote:

> Hi there!
> I have a terrible problem with using the MajorUpgrade element in the 
> current installer we have. We tended to use the Upgrade element having 
> different error messages for different versions by using 
> UpgradeVersion property.
> We wanted this behaviour to persist and to force the Major upgrade for 
> all the software upgrades. (Changing the Product.Id by using a 
> wildcard and using old UpgradeVersion is not the solution as it makes 
> the installer downgrading between builds with no errors - from 2.3.4.6 
> to 2.3.4.2 , having two software versions installed side-by-side).
>
>
> MajorUpgrade:
> ---
> It is not possible to specify the Minimum or Maximum upgradable 
> software version for this element, because the UpgradeVersion is not 
> supported by MajorUpgrade element, which prevents from creating the 
> custom actions with different error codes for particular software versions.
> ---
> Trying to work it around:
>
> Using the MajorUpgrade element side by side with Upgrade element is 
> not possible, as the MajorUpgrade's default Id is set to 
> Product.UpgradeCode which clashes with Upgrade.Id being set the same.
> There are error messages attached to the email.
>
> Could you please help? :)
>
> Thanks!
> Przemyslaw Galera
> Software Engineer
> IndigoVision
> Tel: +44 (0) 131 475 7336 (x336)
> Email: p.gal...@indigovision.com<mailto:p.gal...@indigovision.com>
> www.indigovision.com<http://www.indigovision.com/>
> Complete IP Video Security Solutions
>
>
>
> --
>  Learn Graph Databases - Download FREE O'Reilly Book "Graph 
> Databases" is the definitive new guide to graph databases and their 
> applications. Written by three acclaimed leaders in the field, this 
> first edition is now available. Download your free book today!
> http://p.sf.net/sfu/NeoTech
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


--
"They may forget what you said but they will never forget how you made them 
feel." -- Anonymous
--
Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the 
definitive new guide to graph databases and their applications. Written by 
three acclaimed leaders in the field, this first edition is now available. 
Download your free book today!
http://p.sf.net/sfu/NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their 
applications. Written by three acclaimed leaders in the field, 
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] MajorUpgrade element problems

2014-06-02 Thread David Connet 
>

>Meant maybe try to explain why you are getting downgrading between builds
>with no errors - from 2.3.4.6 to 2.3.4.2  Got ahead of myself.
>


As far as MSI is concerned, those 2 version numbers are the same. MSI only 
looks at the first 3 parts.
http://msdn.microsoft.com/en-us/library/aa370859%28v=vs.85%29.aspx

Dave


--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their 
applications. Written by three acclaimed leaders in the field, 
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] MajorUpgrade element problems

2014-06-02 Thread Jeremiahf 
Meant maybe try to explain why you are getting downgrading between builds
with no errors - from 2.3.4.6 to 2.3.4.2  Got ahead of myself.

J


On Mon, Jun 2, 2014 at 3:15 PM, Jeremiahf  wrote:

> FYI there is not an attachment.
>
> This is how I used to do it before my requirements changed...
>
> will upgrade 1.1.1.1 to 1.1.2.1 and not allow a downgrade.
>
> keep the Upgradecode static and the product/Package Ids to "*"
>
> I use a config.wxi file that I include into product.wxs then reference the
> values with variables.
>
> Up to you how to implement the values though...
>
> Example:
>
> 
>OnlyDetect="no" Property="NEWERVERSIONDETECTED"/>
>Maximum="$(var.InstallerProductVersion)" OnlyDetect="no"
> IncludeMinimum="yes" IncludeMaximum="no"
>   Property="OLDVERSIONBEINGUPGRADED" />
> 
>
> NOT NEWERVERSIONDETECTED
>
> 
>   
>   
>   
> ...
> 
>
> In order to meet version control by the 4th version number you would have
> to use this (It is NOT a good practice.)
>
> There are other threads explaining why in detail. You should also research
> how Microsoft handles version control to get more info in detail.
>
> This allows 1.1.1.1 to upgrade to 1.1.1.2 and not downgrade to 1.1.0.1 or
> 1.1.0.2. Pretty much what you are seeing in a sense.
>  DowngradeErrorMessage="You cannot downgrade to [ProductName]"
> Schedule="afterInstallFinalize"/>
>
>
> 
>   
>   
>
>
> Thank you,
>
> J
>
>
>
> On Mon, Jun 2, 2014 at 10:06 AM, Przemyslaw Galera <
> p.gal...@indigovision.com> wrote:
>
>> Hi there!
>> I have a terrible problem with using the MajorUpgrade element in the
>> current installer we have. We tended to use the Upgrade element having
>> different error messages for different versions by using UpgradeVersion
>> property.
>> We wanted this behaviour to persist and to force the Major upgrade for
>> all the software upgrades. (Changing the Product.Id by using a wildcard and
>> using old UpgradeVersion is not the solution as it makes the installer
>> downgrading between builds with no errors - from 2.3.4.6 to 2.3.4.2 ,
>> having two software versions installed side-by-side).
>>
>>
>> MajorUpgrade:
>> ---
>> It is not possible to specify the Minimum or Maximum upgradable software
>> version for this element, because the UpgradeVersion is not supported by
>> MajorUpgrade element, which prevents from creating the custom actions with
>> different error codes for particular software versions.
>> ---
>> Trying to work it around:
>>
>> Using the MajorUpgrade element side by side with Upgrade element is not
>> possible, as the MajorUpgrade's default Id is set to Product.UpgradeCode
>> which clashes with Upgrade.Id being set the same.
>> There are error messages attached to the email.
>>
>> Could you please help? :)
>>
>> Thanks!
>> Przemyslaw Galera
>> Software Engineer
>> IndigoVision
>> Tel: +44 (0) 131 475 7336 (x336)
>> Email: p.gal...@indigovision.com
>> www.indigovision.com
>> Complete IP Video Security Solutions
>>
>>
>>
>> --
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and their
>> applications. Written by three acclaimed leaders in the field,
>> this first edition is now available. Download your free book today!
>> http://p.sf.net/sfu/NeoTech
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>>
>
>
> --
> "They may forget what you said but they will never forget how you made
> them feel." -- Anonymous
>



-- 
"They may forget what you said but they will never forget how you made them
feel." -- Anonymous
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their 
applications. Written by three acclaimed leaders in the field, 
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] MajorUpgrade element problems

2014-06-02 Thread Jeremiahf 
FYI there is not an attachment.

This is how I used to do it before my requirements changed...

will upgrade 1.1.1.1 to 1.1.2.1 and not allow a downgrade.

keep the Upgradecode static and the product/Package Ids to "*"

I use a config.wxi file that I include into product.wxs then reference the
values with variables.

Up to you how to implement the values though...

Example:


  
  


NOT NEWERVERSIONDETECTED


  
  
  
...


In order to meet version control by the 4th version number you would have
to use this (It is NOT a good practice.)

There are other threads explaining why in detail. You should also research
how Microsoft handles version control to get more info in detail.

This allows 1.1.1.1 to upgrade to 1.1.1.2 and not downgrade to 1.1.0.1 or
1.1.0.2. Pretty much what you are seeing in a sense.




  
  


Thank you,

J



On Mon, Jun 2, 2014 at 10:06 AM, Przemyslaw Galera <
p.gal...@indigovision.com> wrote:

> Hi there!
> I have a terrible problem with using the MajorUpgrade element in the
> current installer we have. We tended to use the Upgrade element having
> different error messages for different versions by using UpgradeVersion
> property.
> We wanted this behaviour to persist and to force the Major upgrade for all
> the software upgrades. (Changing the Product.Id by using a wildcard and
> using old UpgradeVersion is not the solution as it makes the installer
> downgrading between builds with no errors - from 2.3.4.6 to 2.3.4.2 ,
> having two software versions installed side-by-side).
>
>
> MajorUpgrade:
> ---
> It is not possible to specify the Minimum or Maximum upgradable software
> version for this element, because the UpgradeVersion is not supported by
> MajorUpgrade element, which prevents from creating the custom actions with
> different error codes for particular software versions.
> ---
> Trying to work it around:
>
> Using the MajorUpgrade element side by side with Upgrade element is not
> possible, as the MajorUpgrade's default Id is set to Product.UpgradeCode
> which clashes with Upgrade.Id being set the same.
> There are error messages attached to the email.
>
> Could you please help? :)
>
> Thanks!
> Przemyslaw Galera
> Software Engineer
> IndigoVision
> Tel: +44 (0) 131 475 7336 (x336)
> Email: p.gal...@indigovision.com
> www.indigovision.com
> Complete IP Video Security Solutions
>
>
>
> --
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/NeoTech
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


-- 
"They may forget what you said but they will never forget how you made them
feel." -- Anonymous
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their 
applications. Written by three acclaimed leaders in the field, 
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] MajorUpgrade element problems

2014-06-02 Thread Przemyslaw Galera 
Hi there!
I have a terrible problem with using the MajorUpgrade element in the current 
installer we have. We tended to use the Upgrade element having different error 
messages for different versions by using UpgradeVersion property.
We wanted this behaviour to persist and to force the Major upgrade for all the 
software upgrades. (Changing the Product.Id by using a wildcard and using old 
UpgradeVersion is not the solution as it makes the installer downgrading 
between builds with no errors - from 2.3.4.6 to 2.3.4.2 , having two software 
versions installed side-by-side).


MajorUpgrade:
---
It is not possible to specify the Minimum or Maximum upgradable software 
version for this element, because the UpgradeVersion is not supported by 
MajorUpgrade element, which prevents from creating the custom actions with 
different error codes for particular software versions.
---
Trying to work it around:

Using the MajorUpgrade element side by side with Upgrade element is not 
possible, as the MajorUpgrade's default Id is set to Product.UpgradeCode which 
clashes with Upgrade.Id being set the same.
There are error messages attached to the email.

Could you please help? :)

Thanks!
Przemyslaw Galera
Software Engineer
IndigoVision
Tel: +44 (0) 131 475 7336 (x336)
Email: p.gal...@indigovision.com
www.indigovision.com
Complete IP Video Security Solutions

--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their 
applications. Written by three acclaimed leaders in the field, 
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users