Discussion:
[WiX-users] Uninstall a different bundle
Ian Williams
2012-05-07 21:20:03 UTC
Permalink
I'll looking to have my burn bundle invoke uninstall on a different burn bundle if it is detected on a machine. What is the easiest way to accomplish this?

Thanks,
Ian
Ian Brooke
2012-05-08 00:37:55 UTC
Permalink
I hope you don't mind this slightly unusual question!

We have a product currently installed by Installshield (Express 2012) which
we are considering switching to WiX but don't really want to spend the time
doing that if it doesn't solve our problem.

What I really need to determine is if this is standard Windows Installer
behaviour or, if I can stop it happening by switching to WiX.

Here's the problem - We are creating an msi embedded exe which is intended
to either upgrade an existing version if one exists on the target computer
otherwise do a full install. The upgrade has a new Product Code but the
existing Upgrade Code. Both the upgrade and install appear to work fine,
except....

Problem 1. After an upgrade if we check Add/Remove Programs there are 2
entries, one for the old version and one for the new one.

Problem 2. After an upgrade I can use the old version uninstall entry and
that works Ok and leaves the new version Ok. However, if I then uninstall
the new version it leaves an empty application folder (which was originally
created by the old version install) under Program Files(x86).

I'd really like to stop both of these happening.

Thanks for any advise.
Neil Sleightholm
2012-05-08 06:26:03 UTC
Permalink
That is supported by Windows Installer and shouldn't be happening if your MSI is setup correctly even in Installshield. For a major upgrade you need to change the Package code, Product code and version and leave the Upgrade code the same.

WiX 3.5 makes this easy to setup http://wix.sourceforge.net/manual-wix3/major_upgrade.htm, http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/

Here is the setup for v3 http://neilsleightholm.blogspot.co.uk/2009/01/wix-script-for-major-upgrades.html

Neil

-----Original Message-----
From: Ian Brooke [mailto:***@hotmail.com]
Sent: 08 May 2012 01:38
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Add/remove Programs

I hope you don't mind this slightly unusual question!

We have a product currently installed by Installshield (Express 2012) which we are considering switching to WiX but don't really want to spend the time doing that if it doesn't solve our problem.

What I really need to determine is if this is standard Windows Installer behaviour or, if I can stop it happening by switching to WiX.

Here's the problem - We are creating an msi embedded exe which is intended to either upgrade an existing version if one exists on the target computer otherwise do a full install. The upgrade has a new Product Code but the existing Upgrade Code. Both the upgrade and install appear to work fine, except....

Problem 1. After an upgrade if we check Add/Remove Programs there are 2 entries, one for the old version and one for the new one.

Problem 2. After an upgrade I can use the old version uninstall entry and that works Ok and leaves the new version Ok. However, if I then uninstall the new version it leaves an empty application folder (which was originally created by the old version install) under Program Files(x86).

I'd really like to stop both of these happening.

Thanks for any advise.
Ian Brooke
2012-05-08 13:22:13 UTC
Permalink
Thanks for your reply Neil,
I'm not aware of a "Package Code" in Installshield, however the Product Code
has changed and the Version number has changed (from 7.0.2 to 7.0.4) and the
Upgrade Code has remained the same so I have no idea what's going on.
Sounds as though it's an Installshield problem though rather than one with
the Windows Installer.

Looks like I'm going to have to spend the time to switch it to WiX, not
something I wanted to do at this moment in time :(

Ian



-----Original Message-----
From: Neil Sleightholm
Sent: Tuesday, May 08, 2012 12:26 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Add/remove Programs

That is supported by Windows Installer and shouldn't be happening if your
MSI is setup correctly even in Installshield. For a major upgrade you need
to change the Package code, Product code and version and leave the Upgrade
code the same.

WiX 3.5 makes this easy to setup
http://wix.sourceforge.net/manual-wix3/major_upgrade.htm,
http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/

Here is the setup for v3
http://neilsleightholm.blogspot.co.uk/2009/01/wix-script-for-major-upgrades.html

Neil

-----Original Message-----
From: Ian Brooke [mailto:***@hotmail.com]
Sent: 08 May 2012 01:38
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Add/remove Programs

I hope you don't mind this slightly unusual question!

We have a product currently installed by Installshield (Express 2012) which
we are considering switching to WiX but don't really want to spend the time
doing that if it doesn't solve our problem.

What I really need to determine is if this is standard Windows Installer
behaviour or, if I can stop it happening by switching to WiX.

Here's the problem - We are creating an msi embedded exe which is intended
to either upgrade an existing version if one exists on the target computer
otherwise do a full install. The upgrade has a new Product Code but the
existing Upgrade Code. Both the upgrade and install appear to work fine,
except....

Problem 1. After an upgrade if we check Add/Remove Programs there are 2
entries, one for the old version and one for the new one.

Problem 2. After an upgrade I can use the old version uninstall entry and
that works Ok and leaves the new version Ok. However, if I then uninstall
the new version it leaves an empty application folder (which was originally
created by the old version install) under Program Files(x86).

I'd really like to stop both of these happening.

Thanks for any advise.


------------------------------------------------------------------------------
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-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Skildum, Mathew
2012-05-08 13:43:20 UTC
Permalink
You may want to check the values in the Upgrade table. It sounds as though the existing values do not cover the installation you are trying to upgrade. Pay specific attention to the listed upgrade codes and the version settings.

Mat Skildum

-----Original Message-----
From: Ian Brooke [mailto:***@hotmail.com]
Sent: Tuesday, May 08, 2012 8:22 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Add/remove Programs

Thanks for your reply Neil,
I'm not aware of a "Package Code" in Installshield, however the Product Code has changed and the Version number has changed (from 7.0.2 to 7.0.4) and the Upgrade Code has remained the same so I have no idea what's going on.
Sounds as though it's an Installshield problem though rather than one with the Windows Installer.

Looks like I'm going to have to spend the time to switch it to WiX, not something I wanted to do at this moment in time :(

Ian



-----Original Message-----
From: Neil Sleightholm
Sent: Tuesday, May 08, 2012 12:26 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Add/remove Programs

That is supported by Windows Installer and shouldn't be happening if your MSI is setup correctly even in Installshield. For a major upgrade you need to change the Package code, Product code and version and leave the Upgrade code the same.

WiX 3.5 makes this easy to setup
http://wix.sourceforge.net/manual-wix3/major_upgrade.htm,
http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/

Here is the setup for v3
http://neilsleightholm.blogspot.co.uk/2009/01/wix-script-for-major-upgrades.html

Neil

-----Original Message-----
From: Ian Brooke [mailto:***@hotmail.com]
Sent: 08 May 2012 01:38
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Add/remove Programs

I hope you don't mind this slightly unusual question!

We have a product currently installed by Installshield (Express 2012) which we are considering switching to WiX but don't really want to spend the time doing that if it doesn't solve our problem.

What I really need to determine is if this is standard Windows Installer behaviour or, if I can stop it happening by switching to WiX.

Here's the problem - We are creating an msi embedded exe which is intended to either upgrade an existing version if one exists on the target computer otherwise do a full install. The upgrade has a new Product Code but the existing Upgrade Code. Both the upgrade and install appear to work fine, except....

Problem 1. After an upgrade if we check Add/Remove Programs there are 2 entries, one for the old version and one for the new one.

Problem 2. After an upgrade I can use the old version uninstall entry and that works Ok and leaves the new version Ok. However, if I then uninstall the new version it leaves an empty application folder (which was originally created by the old version install) under Program Files(x86).

I'd really like to stop both of these happening.

Thanks for any advise.


------------------------------------------------------------------------------
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-***@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-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Pally Sandher
2012-05-08 13:46:56 UTC
Permalink
Are you sure you have RemoveExistingProducts scheduled?

Sounds to me like when you install the later version, it's incrementing the Component Reference count which is why uninstalling the old one works fine (all it does is decrement the Component Reference counts) & would explain why the directory isn't being removed when the new version is uninstalled because it didn't create it in the first place. RemoveExistingProducts should be scheduled if you want to do a Major Upgrade which is what it sounds like you want to do (as in uninstall the old version before installing the new one or upgrade the old version to the new one) -> http://msdn.microsoft.com/en-us/library/windows/desktop/aa371197.aspx

Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com

**Design, Simulate + Innovate with the <Virtual Environment>**
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP
Email Disclaimer



-----Original Message-----
From: Ian Brooke [mailto:***@hotmail.com]
Sent: 08 May 2012 14:26
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Add/remove Programs

Thanks for your reply Neil,
I'm not aware of a "Package Code" in Installshield, however the Product Code
has changed and the Version number has changed (from 7.0.2 to 7.0.4) and the
Upgrade Code has remained the same so I have no idea what's going on.
Sounds as though it's an Installshield problem though rather than one with
the Windows Installer.

Looks like I'm going to have to spend the time to switch it to WiX, not
something I wanted to do at this moment in time :(

Ian



-----Original Message-----
From: Neil Sleightholm
Sent: Tuesday, May 08, 2012 12:26 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Add/remove Programs

That is supported by Windows Installer and shouldn't be happening if your
MSI is setup correctly even in Installshield. For a major upgrade you need
to change the Package code, Product code and version and leave the Upgrade
code the same.

WiX 3.5 makes this easy to setup
http://wix.sourceforge.net/manual-wix3/major_upgrade.htm,
http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/

Here is the setup for v3
http://neilsleightholm.blogspot.co.uk/2009/01/wix-script-for-major-upgrades.html

Neil

-----Original Message-----
From: Ian Brooke [mailto:***@hotmail.com]
Sent: 08 May 2012 01:38
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Add/remove Programs

I hope you don't mind this slightly unusual question!

We have a product currently installed by Installshield (Express 2012) which
we are considering switching to WiX but don't really want to spend the time
doing that if it doesn't solve our problem.

What I really need to determine is if this is standard Windows Installer
behaviour or, if I can stop it happening by switching to WiX.

Here's the problem - We are creating an msi embedded exe which is intended
to either upgrade an existing version if one exists on the target computer
otherwise do a full install. The upgrade has a new Product Code but the
existing Upgrade Code. Both the upgrade and install appear to work fine,
except....

Problem 1. After an upgrade if we check Add/Remove Programs there are 2
entries, one for the old version and one for the new one.

Problem 2. After an upgrade I can use the old version uninstall entry and
that works Ok and leaves the new version Ok. However, if I then uninstall
the new version it leaves an empty application folder (which was originally
created by the old version install) under Program Files(x86).

I'd really like to stop both of these happening.

Thanks for any advise.


------------------------------------------------------------------------------
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-***@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-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Ian Brooke
2012-05-08 15:35:21 UTC
Permalink
I'm sorry to keep going on about this problem. Despite the various suggestions (some of which I have to admit were over my head!) I am still uncertain where this problem lies, there seems to be various candidates - a problem with the original install, a problem with Installshield or a problem with Windows Installer. The second of these I could I believe fix by switching to WiX, the others I could not.

I went through the InstallLog from the latest attempt and found this section:
Begin SetAllUsers()
InstallShield 9:22:28: Getting records from Upgrade table
InstallShield 9:22:28: UpgradeCode: {B6888838-F1BE-45AC-B27A-BE69104843CF} MinVersion: MaxVersion: Language: 1033 Attributes: 1024
InstallShield 9:22:28: Checking related product {030062FD-BFBE-4443-A22A-668F27A8D718}
InstallShield 9:22:28: AppName {030062FD-BFBE-4443-A22A-668F27A8D718} 1033 7.0.2 ***Not Related***
InstallShield 9:22:28: No related products for UpgradeCode {B6888838-F1BE-45AC-B27A-BE69104843CF} found
InstallShield 9:22:28: UpgradeCode: {B6888838-F1BE-45AC-B27A-BE69104843CF} MinVersion: 7.1.0 MaxVersion: Language: Attributes: 2
InstallShield 9:22:28: Checking related product {030062FD-BFBE-4443-A22A-668F27A8D718}
InstallShield 9:22:28: No related products for UpgradeCode {B6888838-F1BE-45AC-B27A-BE69104843CF} found
InstallShield 9:22:28: End SetAllUsers()

To me that "***Not Related***" seems significant! But I don't know why it's saying this. I was previously specifying Min and a Max version number with Min=7.0.0 and Max=7.0.3 but this wasn't working so I removed them to see if it would help, it didn't.

Can anyone tell me what "Attributes: 1024" means and is this likely to affect anything?

I really don't know why the new version 7.1.0 is shown with a blank language code as one was specified. Is that the cause?

More importantly, can anyone tell me if this looks like an issue that I could fix by switching to WiX?

Many thanks
Ian



-----Original Message-----
From: Ian Brooke
Sent: Tuesday, May 08, 2012 7:22 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Add/remove Programs

Thanks for your reply Neil,
I'm not aware of a "Package Code" in Installshield, however the Product Code
has changed and the Version number has changed (from 7.0.2 to 7.0.4) and the
Upgrade Code has remained the same so I have no idea what's going on.
Sounds as though it's an Installshield problem though rather than one with
the Windows Installer.

Looks like I'm going to have to spend the time to switch it to WiX, not
something I wanted to do at this moment in time :(

Ian



-----Original Message-----
From: Neil Sleightholm
Sent: Tuesday, May 08, 2012 12:26 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Add/remove Programs

That is supported by Windows Installer and shouldn't be happening if your
MSI is setup correctly even in Installshield. For a major upgrade you need
to change the Package code, Product code and version and leave the Upgrade
code the same.

WiX 3.5 makes this easy to setup
http://wix.sourceforge.net/manual-wix3/major_upgrade.htm,
http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/

Here is the setup for v3
http://neilsleightholm.blogspot.co.uk/2009/01/wix-script-for-major-upgrades.html

Neil

-----Original Message-----
From: Ian Brooke [mailto:***@hotmail.com]
Sent: 08 May 2012 01:38
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Add/remove Programs

I hope you don't mind this slightly unusual question!

We have a product currently installed by Installshield (Express 2012) which
we are considering switching to WiX but don't really want to spend the time
doing that if it doesn't solve our problem.

What I really need to determine is if this is standard Windows Installer
behaviour or, if I can stop it happening by switching to WiX.

Here's the problem - We are creating an msi embedded exe which is intended
to either upgrade an existing version if one exists on the target computer
otherwise do a full install. The upgrade has a new Product Code but the
existing Upgrade Code. Both the upgrade and install appear to work fine,
except....

Problem 1. After an upgrade if we check Add/Remove Programs there are 2
entries, one for the old version and one for the new one.

Problem 2. After an upgrade I can use the old version uninstall entry and
that works Ok and leaves the new version Ok. However, if I then uninstall
the new version it leaves an empty application folder (which was originally
created by the old version install) under Program Files(x86).

I'd really like to stop both of these happening.

Thanks for any advise.


------------------------------------------------------------------------------
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-***@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-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Wilson, Phil
2012-05-08 17:52:04 UTC
Permalink
Not sure if this has been mentioned, but one of the gotchas is that the previous version of the install might be installed per-user instead of per-machine. A per-machine install will not upgrade a per user (and vice versa) so you get two entries in ARP. That's an InstallShield log, not an MSI log, but "not related" might be trying to tell you it's not the same install context as the incoming one.

I vaguely recall that InstallShield tries to be clever in this area, that's why that code is called SetAllUsers. When you do an upgrade I think it might make an effort to match ALLUSERS with the installed product it found (so you can do the upgrade). If anything is going on there, it's an InstallShield thing. Clearly you need to put versions in your Upgrade table that match the versions you want to upgrade, as InstallShield is using those records to figure out what upgrade it will do.

Phil W

-----Original Message-----
From: Ian Brooke [mailto:***@hotmail.com]
Sent: Tuesday, May 08, 2012 8:35 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Add/remove Programs

I'm sorry to keep going on about this problem. Despite the various suggestions (some of which I have to admit were over my head!) I am still uncertain where this problem lies, there seems to be various candidates - a problem with the original install, a problem with Installshield or a problem with Windows Installer. The second of these I could I believe fix by switching to WiX, the others I could not.

I went through the InstallLog from the latest attempt and found this section:
Begin SetAllUsers()
InstallShield 9:22:28: Getting records from Upgrade table
InstallShield 9:22:28: UpgradeCode: {B6888838-F1BE-45AC-B27A-BE69104843CF} MinVersion: MaxVersion: Language: 1033 Attributes: 1024
InstallShield 9:22:28: Checking related product {030062FD-BFBE-4443-A22A-668F27A8D718}
InstallShield 9:22:28: AppName {030062FD-BFBE-4443-A22A-668F27A8D718} 1033 7.0.2 ***Not Related***
InstallShield 9:22:28: No related products for UpgradeCode {B6888838-F1BE-45AC-B27A-BE69104843CF} found
InstallShield 9:22:28: UpgradeCode: {B6888838-F1BE-45AC-B27A-BE69104843CF} MinVersion: 7.1.0 MaxVersion: Language: Attributes: 2
InstallShield 9:22:28: Checking related product {030062FD-BFBE-4443-A22A-668F27A8D718}
InstallShield 9:22:28: No related products for UpgradeCode {B6888838-F1BE-45AC-B27A-BE69104843CF} found InstallShield 9:22:28: End SetAllUsers()

To me that "***Not Related***" seems significant! But I don't know why it's saying this. I was previously specifying Min and a Max version number with Min=7.0.0 and Max=7.0.3 but this wasn't working so I removed them to see if it would help, it didn't.

Can anyone tell me what "Attributes: 1024" means and is this likely to affect anything?

I really don't know why the new version 7.1.0 is shown with a blank language code as one was specified. Is that the cause?

More importantly, can anyone tell me if this looks like an issue that I could fix by switching to WiX?

Many thanks
Ian



-----Original Message-----
From: Ian Brooke
Sent: Tuesday, May 08, 2012 7:22 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Add/remove Programs

Thanks for your reply Neil,
I'm not aware of a "Package Code" in Installshield, however the Product Code has changed and the Version number has changed (from 7.0.2 to 7.0.4) and the Upgrade Code has remained the same so I have no idea what's going on.
Sounds as though it's an Installshield problem though rather than one with the Windows Installer.

Looks like I'm going to have to spend the time to switch it to WiX, not something I wanted to do at this moment in time :(

Ian



-----Original Message-----
From: Neil Sleightholm
Sent: Tuesday, May 08, 2012 12:26 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Add/remove Programs

That is supported by Windows Installer and shouldn't be happening if your MSI is setup correctly even in Installshield. For a major upgrade you need to change the Package code, Product code and version and leave the Upgrade code the same.

WiX 3.5 makes this easy to setup
http://wix.sourceforge.net/manual-wix3/major_upgrade.htm,
http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/

Here is the setup for v3
http://neilsleightholm.blogspot.co.uk/2009/01/wix-script-for-major-upgrades.html

Neil

-----Original Message-----
From: Ian Brooke [mailto:***@hotmail.com]
Sent: 08 May 2012 01:38
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Add/remove Programs

I hope you don't mind this slightly unusual question!

We have a product currently installed by Installshield (Express 2012) which we are considering switching to WiX but don't really want to spend the time doing that if it doesn't solve our problem.

What I really need to determine is if this is standard Windows Installer behaviour or, if I can stop it happening by switching to WiX.

Here's the problem - We are creating an msi embedded exe which is intended to either upgrade an existing version if one exists on the target computer otherwise do a full install. The upgrade has a new Product Code but the existing Upgrade Code. Both the upgrade and install appear to work fine, except....

Problem 1. After an upgrade if we check Add/Remove Programs there are 2 entries, one for the old version and one for the new one.

Problem 2. After an upgrade I can use the old version uninstall entry and that works Ok and leaves the new version Ok. However, if I then uninstall the new version it leaves an empty application folder (which was originally created by the old version install) under Program Files(x86).

I'd really like to stop both of these happening.

Thanks for any advise.


------------------------------------------------------------------------------
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-***@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-***@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-***@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-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


*** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx.

You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail ***@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates).
Rob Mensching
2012-05-09 05:25:06 UTC
Permalink
Add a RelatedBundle element with Id same as the UpgradeCode of the old
Bundle and Action="Upgrade". Oh and make sure your new Bundle's version is
higher.
Post by Ian Williams
I'll looking to have my burn bundle invoke uninstall on a different burn
bundle if it is detected on a machine. What is the easiest way to
accomplish this?
Thanks,
Ian
------------------------------------------------------------------------------
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
https://lists.sourceforge.net/lists/listinfo/wix-users
--
virtually, Rob Mensching - http://RobMensching.com LLC
Loading...