Re: [WiX-users] Bug? UpgradeVersion element causing LGHT0094 error
1. Agreed. I find it easier to change UpgradeCodes, rather than do the UpgradeVersion dance. In my mind, I think about UpgradeCodes as defining whether the package installs SxS or not. 2. You can override the default planning of Burn for packages by returning your requested state for that package to Burn from OnPlanPackageBegin(). I'll have to check but I think you can do the same by returning the operation you want from OnPlanRelatedBundle()... but I would not be surprised if that was not supported... becuase downgrading is pretty weird. If 2 is not supported for Bundles, feel free to open a bug. On Thu, Jul 12, 2012 at 2:20 PM, Don Walker wrote: > > Don Walker wrote > > > > Here is the situation: > > > > 1. We allow multiple versions of our product to be installed at the same > > time if they have a different Major.Minor version. I don't believe that > > the MajorUpgrade element supports this option. The UpgradeVersion > elements > > shown should provide for this. > > 2. Within the same Major.Minor version the user can upgrade or downgrade > > the product. The AllowDowngrades attribute of the MajorUpgrade element > > does support this. > > > > I realize that there could be other approaches to implementing this such > > as using a new UpgradeCode for each Major.Minor version. I thought that > my > > current approach would be closer to what Windows Installer intended. > > Comments? > > > > This seems to work ok with simple msi files. However, trying to get Burn to > do what I want is a puzzle I need help with: > > 1. It appears that I will have to use a new UpgradeCode for each > Major.Minor > version of a bundle since I don't have the equivalent of UpgradeVersion > elements for bundles. If I do this I would be tempted to do the same with > the msi files that make up the bundle in order to keep things consistent. > 2. I can't figure out any way to get a bundle to downgrade a version. It > appears that I'll have to flag the downgrade as an error and require the > user to uninstall the previous bundle. I guess you could argue that the > need > to downgrade an install should be rare enough that we don't need to make it > convenient. > > let me know if I've missed anything or there are other approaches. > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bug-UpgradeVersion-element-causing-LGHT0094-error-tp7579387p7579408.html > Sent from the wix-users mailing list archive at Nabble.com. > > > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bug? UpgradeVersion element causing LGHT0094 error
Don Walker wrote > > Here is the situation: > > 1. We allow multiple versions of our product to be installed at the same > time if they have a different Major.Minor version. I don't believe that > the MajorUpgrade element supports this option. The UpgradeVersion elements > shown should provide for this. > 2. Within the same Major.Minor version the user can upgrade or downgrade > the product. The AllowDowngrades attribute of the MajorUpgrade element > does support this. > > I realize that there could be other approaches to implementing this such > as using a new UpgradeCode for each Major.Minor version. I thought that my > current approach would be closer to what Windows Installer intended. > Comments? > This seems to work ok with simple msi files. However, trying to get Burn to do what I want is a puzzle I need help with: 1. It appears that I will have to use a new UpgradeCode for each Major.Minor version of a bundle since I don't have the equivalent of UpgradeVersion elements for bundles. If I do this I would be tempted to do the same with the msi files that make up the bundle in order to keep things consistent. 2. I can't figure out any way to get a bundle to downgrade a version. It appears that I'll have to flag the downgrade as an error and require the user to uninstall the previous bundle. I guess you could argue that the need to downgrade an install should be rare enough that we don't need to make it convenient. let me know if I've missed anything or there are other approaches. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bug-UpgradeVersion-element-causing-LGHT0094-error-tp7579387p7579408.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bug? UpgradeVersion element causing LGHT0094 error
Rob Mensching-7 wrote > > Or use MajorUpgrade element. > I don't think that the MajorUpgrade element gives me the flexibility that I need. My assumptions (and what I believe to be best practice) are: 1. The UpgradeCode is fixed for all versions of the product. 2. The Product Id is set to "*" so a new GUID will be generated for each build of the installer. Here is the situation: 1. We allow multiple versions of our product to be installed at the same time if they have a different Major.Minor version. I don't believe that the MajorUpgrade element supports this option. The UpgradeVersion elements shown should provide for this. 2. Within the same Major.Minor version the user can upgrade or downgrade the product. The AllowDowngrades attribute of the MajorUpgrade element does support this. I realize that there could be other approaches to implementing this such as using a new UpgradeCode for each Major.Minor version. I thought that my current approach would be closer to what Windows Installer intended. Comments? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bug-UpgradeVersion-element-causing-LGHT0094-error-tp7579387p7579403.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bug? UpgradeVersion element causing LGHT0094 error
Or use MajorUpgrade element.
On Wed, Jul 11, 2012 at 12:36 PM, Don Walker wrote:
>
> Chad Petersen wrote
> >
> > I was able to get past this error in your example by adding this inside
> > the Fragment
> >
> >
> >
> >
> >
>
> Scheduling RemoveExistingProducts worked for me too. Ironically, I had just
> finished reading about scheduling it in the Windows Installer help and was
> considering scheduling it after InstallFinalize. I wanted to resolve this
> problem before continuing :-{
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bug-UpgradeVersion-element-causing-LGHT0094-error-tp7579387p7579389.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
virtually,
Rob Mensching
http://RobMensching.com LLC
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bug? UpgradeVersion element causing LGHT0094 error
Chad Petersen wrote
>
> I was able to get past this error in your example by adding this inside
> the Fragment
>
>
>
>
>
Scheduling RemoveExistingProducts worked for me too. Ironically, I had just
finished reading about scheduling it in the Windows Installer help and was
considering scheduling it after InstallFinalize. I wanted to resolve this
problem before continuing :-{
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bug-UpgradeVersion-element-causing-LGHT0094-error-tp7579387p7579389.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bug? UpgradeVersion element causing LGHT0094 error
I was able to get past this error in your example by adding this inside the Fragment -Original Message- From: Don Walker [mailto:don.wal...@versaterm.com] Sent: Wednesday, July 11, 2012 8:49 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bug? UpgradeVersion element causing LGHT0094 error In WiX version 3.6.3109.0 I am getting the following build error: Product.wxs(16,0): error LGHT0094: Unresolved reference to symbol 'WixAction:InstallExecuteSequence/RemoveExistingProducts' in section 'Product:*'. The same error appears for line 18. My test example follows: http://schemas.microsoft.com/wix/2006/wi";> let me know if this is a bug and I'll file an official bug report. If not, let me know what I did wrong. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bug? UpgradeVersion element causing LGHT0094 error
In WiX version 3.6.3109.0 I am getting the following build error: Product.wxs(16,0): error LGHT0094: Unresolved reference to symbol 'WixAction:InstallExecuteSequence/RemoveExistingProducts' in section 'Product:*'. The same error appears for line 18. My test example follows: http://schemas.microsoft.com/wix/2006/wi";> let me know if this is a bug and I'll file an official bug report. If not, let me know what I did wrong. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
