Re: [WiX-users] Hiding UpgradeCode Attribute Warning
Why do you need a new UpgradeCode all the time? _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 10:45 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning How do I auto-gen an UpgradeCode? * isn't a valid entry for UpgradeCode. Do I actually need the build process to go in and build a new code? Christoph -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
How do I auto-gen an UpgradeCode? * isn't a valid entry for UpgradeCode. Do I actually need the build process to go in and build a new code? Christoph -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Tuesday, May 26, 2015 1:06 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning To say that you don't' have time to do it right because the other team is too busy fixing bugs and adding features is planning to fail. If the application is using and deploying custom COM objects, reg-free is the only way you are going to be able to support multiple versions on the same machine. I would start by ignoring all of the existing installs, start fresh in a new folder. To support multiple versions, you'll need to auto-gen the UpgradeCode, and either auto-gen the component ID's, or change the paths so that the * component IDs get updated for each version. You'll also need to deploy them to a version specific installation folder. -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 11:22 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning We have most definitely considered that. But then comes the next issue. In order to make those changes, we need to make application changes. But we can't do that because the other team is so busy still fixing other defects and adding new features, that we can hardly coordinate enough time to talk about the installer, let alone talk about changing the application. Also, we have customers in the field that will be using the old version and new version on the same machine, so we can't make any changes to existing applications. Christoph -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Tuesday, May 26, 2015 12:13 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning So in your cleanup efforts, why not cut ties with the old versions completely? Put it in a new and unique folder, and handle the common files. I don't know if any of them use COM, the GAC, or if you have access or the ability to request a rebuild of the application. For COM, I'd suggest eliminating the inter-dependency of multiple versions (since it sounds like the rules of COM weren't followed for backwards compatibility) by using a manifest to do Reg-Free COM. If you need to add a manifest without rebuilding the application, mt.exe from the Windows SDK's can do that. -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 11:02 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Jacob, I'm already sabotaged. The scenario is: Another team developed an InstallShield package for an msi, and a Wise package for an exe. The packages didn't even match in what they were delivering (a headache in itself). They didn't follow the installer rules. What they did, was deliver to a temp directory, then ran a custom action .bat file to copy the files to a version directory within the main directory for the product. But there's also common files between versions, so there's logic about whether to replace those or not. Anyways, it breaks all the rules about how to specify components, so the installer has no idea of what files are actually there. So there were so many installation defects, that now we had to come in to clean up their install. But we can't reuse GUIDs and their program doesn't even show up in the add/remove programs. And just to make everything more fun, you can have multiple versions of the product installed at the same time. It's causing a headache, because you can't do an upgrade, but we can't even follow normal rules of adding shared GUIDs to components between versions. We have resorted to completely removing the uninstall option if a legacy product is installed (ridiculous, right?). So I need to suppress the upgrade, because the idea of an upgrade is really just an install of a different version. If you have a way better way to go around this, please feel free to educate me. Because this is also my first WiX project, and I'm just working with what I got. Christoph -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Tuesday, May 26, 2015 11:52 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Why would you want to intentionally sabotage yourself? Provide an UpgradeCode, and just don't release any upgrades. -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Tuesday, May 26, 2015 10:33 AM To: General discussion about the WiX toolset. Subject: Re: [WiX
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
As I had described in my other emails, I am in a situation where our upgrades are really just an install of another version. They need to exist side-by-side. But I need to remove the warning that is brought up that I don't have an upgrade code, and the upgrade code can't have the * value. Christoph -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: Tuesday, May 26, 2015 1:52 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Why do you need a new UpgradeCode all the time? _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 10:45 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning How do I auto-gen an UpgradeCode? * isn't a valid entry for UpgradeCode. Do I actually need the build process to go in and build a new code? Christoph -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
Yes, I read that. However, that doesn't say why you need a unique UpgradeCode all the time. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 11:18 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning As I had described in my other emails, I am in a situation where our upgrades are really just an install of another version. They need to exist side-by-side. But I need to remove the warning that is brought up that I don't have an upgrade code, and the upgrade code can't have the * value. Christoph -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
Having the same UpgradeCode for 2 installers causes the installer to initiate an upgrade instead of an additional installation. I want a new UpgradeCode each build, so that no 2 packages will have the same UpgradeCode, allowing us to install the multiple versions. If there is a better way to do this, I am open to it. Christoph -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: Tuesday, May 26, 2015 2:27 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Yes, I read that. However, that doesn't say why you need a unique UpgradeCode all the time. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 11:18 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning As I had described in my other emails, I am in a situation where our upgrades are really just an install of another version. They need to exist side-by-side. But I need to remove the warning that is brought up that I don't have an upgrade code, and the upgrade code can't have the * value. Christoph -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
Thank you for the answer John! An additional question: What attributes do I need to include for the MajorUpgrade element? I looked at the documentation and it isn't immediately clear to me. I want to still allow multiple versions of the product to be installed. They'll have the same GUIDs, though, since we can't automatically generate the GUIDs every build for the UpgradeCode. So if I say Disallow=yes for MajorUpgrade, will I still be able to have multiple versions installed? Christoph -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Tuesday, May 26, 2015 11:33 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Provide the UpgradeCode and suppress upgrades in the MajorUpgrade element. -- John Merryweather Cooper Senior Software Engineer | Integration Development Group | Enterprise Notification Service Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 10:27 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Hiding UpgradeCode Attribute Warning The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin. I am getting the following error for my project: The Product/@UpgradeCode attribute was not found; it is strongly recommended to ensure that this product can be upgraded. I am WELL aware of the following: 1) You should always have an upgrade code, even if you don't plan on upgrading. But for this specific product, I am positive I do not want the upgrade code. We will never support an upgrade for this product, due to other incredibly obnoxious issues. 2) This is a warning, not an error. Unfortunately, for releasing we MUST specify to treat warnings as errors, so I need to mitigate this error. My question is, how do I suppress this error since it doesn't have an error code, just a message? Or is there anything to include in the code to mitigate the error? Thank you, Christoph Griesshammer GE Healthcare IT Software Engineer E: christoph.griessham...@ge.commailto:christoph.griessham...@ge.com http://www.gehealthcare.comhttp://www.gehealthcare.com/ 116 Huntington Ave Boston, MA, USA 02116-5744 GE Imagination at Work -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
Despite its name, UpgradeCode can serve other very useful purposes... like detection. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: David Connet [mailto:d...@agilityrecordbook.com] Sent: Tuesday, May 26, 2015 8:54 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning I am WELL aware of the following: 1) You should always have an upgrade code, even if you don't plan on upgrading. But for this specific product, I am positive I do not want the upgrade code. We will never support an upgrade for this product, due to other incredibly obnoxious issues. Haha. Famous last words! :) (Several times we've been absolutely assured that X will _never_ happen. So we base our architecture on that. A time duration=soon/ later, we need to implement X. sigh. We (devs) now architect with the assumption that X will happen.) Seriously, just set the upgrade code. GUIDs are cheap. If you will never upgrade, nothing is lost. But if you do ... major pain averted! Dave -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
We have most definitely considered that. But then comes the next issue. In order to make those changes, we need to make application changes. But we can't do that because the other team is so busy still fixing other defects and adding new features, that we can hardly coordinate enough time to talk about the installer, let alone talk about changing the application. Also, we have customers in the field that will be using the old version and new version on the same machine, so we can't make any changes to existing applications. Christoph -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Tuesday, May 26, 2015 12:13 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning So in your cleanup efforts, why not cut ties with the old versions completely? Put it in a new and unique folder, and handle the common files. I don't know if any of them use COM, the GAC, or if you have access or the ability to request a rebuild of the application. For COM, I'd suggest eliminating the inter-dependency of multiple versions (since it sounds like the rules of COM weren't followed for backwards compatibility) by using a manifest to do Reg-Free COM. If you need to add a manifest without rebuilding the application, mt.exe from the Windows SDK's can do that. -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 11:02 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Jacob, I'm already sabotaged. The scenario is: Another team developed an InstallShield package for an msi, and a Wise package for an exe. The packages didn't even match in what they were delivering (a headache in itself). They didn't follow the installer rules. What they did, was deliver to a temp directory, then ran a custom action .bat file to copy the files to a version directory within the main directory for the product. But there's also common files between versions, so there's logic about whether to replace those or not. Anyways, it breaks all the rules about how to specify components, so the installer has no idea of what files are actually there. So there were so many installation defects, that now we had to come in to clean up their install. But we can't reuse GUIDs and their program doesn't even show up in the add/remove programs. And just to make everything more fun, you can have multiple versions of the product installed at the same time. It's causing a headache, because you can't do an upgrade, but we can't even follow normal rules of adding shared GUIDs to components between versions. We have resorted to completely removing the uninstall option if a legacy product is installed (ridiculous, right?). So I need to suppress the upgrade, because the idea of an upgrade is really just an install of a different version. If you have a way better way to go around this, please feel free to educate me. Because this is also my first WiX project, and I'm just working with what I got. Christoph -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Tuesday, May 26, 2015 11:52 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Why would you want to intentionally sabotage yourself? Provide an UpgradeCode, and just don't release any upgrades. -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Tuesday, May 26, 2015 10:33 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Provide the UpgradeCode and suppress upgrades in the MajorUpgrade element. -- John Merryweather Cooper Senior Software Engineer | Integration Development Group | Enterprise Notification Service Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 10:27 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Hiding UpgradeCode Attribute Warning The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin. I am getting the following error for my project: The Product/@UpgradeCode attribute was not found; it is strongly recommended to ensure that this product can be upgraded. I am WELL aware of the following: 1) You should always have an upgrade code, even if you don't plan on upgrading. But for this specific product, I am positive I do not want the upgrade code. We will never support an upgrade for this product, due to other incredibly obnoxious issues. 2) This is a warning, not an error. Unfortunately, for releasing we MUST specify to treat warnings as errors, so I
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
Provide the UpgradeCode and suppress upgrades in the MajorUpgrade element. -- John Merryweather Cooper Senior Software Engineer | Integration Development Group | Enterprise Notification Service Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 10:27 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Hiding UpgradeCode Attribute Warning The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin. I am getting the following error for my project: The Product/@UpgradeCode attribute was not found; it is strongly recommended to ensure that this product can be upgraded. I am WELL aware of the following: 1) You should always have an upgrade code, even if you don't plan on upgrading. But for this specific product, I am positive I do not want the upgrade code. We will never support an upgrade for this product, due to other incredibly obnoxious issues. 2) This is a warning, not an error. Unfortunately, for releasing we MUST specify to treat warnings as errors, so I need to mitigate this error. My question is, how do I suppress this error since it doesn't have an error code, just a message? Or is there anything to include in the code to mitigate the error? Thank you, Christoph Griesshammer GE Healthcare IT Software Engineer E: christoph.griessham...@ge.commailto:christoph.griessham...@ge.com http://www.gehealthcare.comhttp://www.gehealthcare.com/ 116 Huntington Ave Boston, MA, USA 02116-5744 GE Imagination at Work -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
So in your cleanup efforts, why not cut ties with the old versions completely? Put it in a new and unique folder, and handle the common files. I don't know if any of them use COM, the GAC, or if you have access or the ability to request a rebuild of the application. For COM, I'd suggest eliminating the inter-dependency of multiple versions (since it sounds like the rules of COM weren't followed for backwards compatibility) by using a manifest to do Reg-Free COM. If you need to add a manifest without rebuilding the application, mt.exe from the Windows SDK's can do that. -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 11:02 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Jacob, I'm already sabotaged. The scenario is: Another team developed an InstallShield package for an msi, and a Wise package for an exe. The packages didn't even match in what they were delivering (a headache in itself). They didn't follow the installer rules. What they did, was deliver to a temp directory, then ran a custom action .bat file to copy the files to a version directory within the main directory for the product. But there's also common files between versions, so there's logic about whether to replace those or not. Anyways, it breaks all the rules about how to specify components, so the installer has no idea of what files are actually there. So there were so many installation defects, that now we had to come in to clean up their install. But we can't reuse GUIDs and their program doesn't even show up in the add/remove programs. And just to make everything more fun, you can have multiple versions of the product installed at the same time. It's causing a headache, because you can't do an upgrade, but we can't even follow normal rules of adding shared GUIDs to components between versions. We have resorted to completely removing the uninstall option if a legacy product is installed (ridiculous, right?). So I need to suppress the upgrade, because the idea of an upgrade is really just an install of a different version. If you have a way better way to go around this, please feel free to educate me. Because this is also my first WiX project, and I'm just working with what I got. Christoph -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Tuesday, May 26, 2015 11:52 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Why would you want to intentionally sabotage yourself? Provide an UpgradeCode, and just don't release any upgrades. -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Tuesday, May 26, 2015 10:33 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Provide the UpgradeCode and suppress upgrades in the MajorUpgrade element. -- John Merryweather Cooper Senior Software Engineer | Integration Development Group | Enterprise Notification Service Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 10:27 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Hiding UpgradeCode Attribute Warning The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin. I am getting the following error for my project: The Product/@UpgradeCode attribute was not found; it is strongly recommended to ensure that this product can be upgraded. I am WELL aware of the following: 1) You should always have an upgrade code, even if you don't plan on upgrading. But for this specific product, I am positive I do not want the upgrade code. We will never support an upgrade for this product, due to other incredibly obnoxious issues. 2) This is a warning, not an error. Unfortunately, for releasing we MUST specify to treat warnings as errors, so I need to mitigate this error. My question is, how do I suppress this error since it doesn't have an error code, just a message? Or is there anything to include in the code to mitigate the error? Thank you, Christoph Griesshammer GE Healthcare IT Software Engineer E: christoph.griessham...@ge.commailto:christoph.griessham...@ge.com http://www.gehealthcare.comhttp://www.gehealthcare.com/ 116 Huntington Ave Boston, MA, USA 02116-5744 GE Imagination at Work -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
Why would you want to intentionally sabotage yourself? Provide an UpgradeCode, and just don't release any upgrades. -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Tuesday, May 26, 2015 10:33 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Provide the UpgradeCode and suppress upgrades in the MajorUpgrade element. -- John Merryweather Cooper Senior Software Engineer | Integration Development Group | Enterprise Notification Service Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 10:27 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Hiding UpgradeCode Attribute Warning The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin. I am getting the following error for my project: The Product/@UpgradeCode attribute was not found; it is strongly recommended to ensure that this product can be upgraded. I am WELL aware of the following: 1) You should always have an upgrade code, even if you don't plan on upgrading. But for this specific product, I am positive I do not want the upgrade code. We will never support an upgrade for this product, due to other incredibly obnoxious issues. 2) This is a warning, not an error. Unfortunately, for releasing we MUST specify to treat warnings as errors, so I need to mitigate this error. My question is, how do I suppress this error since it doesn't have an error code, just a message? Or is there anything to include in the code to mitigate the error? Thank you, Christoph Griesshammer GE Healthcare IT Software Engineer E: christoph.griessham...@ge.commailto:christoph.griessham...@ge.com http://www.gehealthcare.comhttp://www.gehealthcare.com/ 116 Huntington Ave Boston, MA, USA 02116-5744 GE Imagination at Work -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
I'm understanding now that I can use the MajorUpgrade element while providing a UpgradeCode to achieve what I need. I'm just not sure from the documentation yet. What attributes do I need to include for the MajorUpgrade element? I looked at the documentation and it isn't immediately clear to me. I need to still allow multiple versions of the product to be installed. They'll have the same GUIDs, though, since we can't automatically generate the GUIDs every build for the UpgradeCode. So if I say Disallow=yes for MajorUpgrade, will I still be able to have multiple versions installed? Christoph -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: Tuesday, May 26, 2015 12:16 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Despite its name, UpgradeCode can serve other very useful purposes... like detection. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: David Connet [mailto:d...@agilityrecordbook.com] Sent: Tuesday, May 26, 2015 8:54 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning I am WELL aware of the following: 1) You should always have an upgrade code, even if you don't plan on upgrading. But for this specific product, I am positive I do not want the upgrade code. We will never support an upgrade for this product, due to other incredibly obnoxious issues. Haha. Famous last words! :) (Several times we've been absolutely assured that X will _never_ happen. So we base our architecture on that. A time duration=soon/ later, we need to implement X. sigh. We (devs) now architect with the assumption that X will happen.) Seriously, just set the upgrade code. GUIDs are cheap. If you will never upgrade, nothing is lost. But if you do ... major pain averted! Dave -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
Nevermind. I realized my big mistake here is that if you don't specify the MajorUpgrade tag, then you don't have any upgrade support. I was writing the documentation incorrectly, and was under the false impression that by specifying the UpgradeCode you automatically allow the standard upgrade ability, but that's not the case. I have added the UpgradeCode but left out the MajorUpgrade element. Christoph -Original Message- From: Griesshammer, Christoph (GE Healthcare) Sent: Tuesday, May 26, 2015 2:33 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Having the same UpgradeCode for 2 installers causes the installer to initiate an upgrade instead of an additional installation. I want a new UpgradeCode each build, so that no 2 packages will have the same UpgradeCode, allowing us to install the multiple versions. If there is a better way to do this, I am open to it. Christoph -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: Tuesday, May 26, 2015 2:27 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Yes, I read that. However, that doesn't say why you need a unique UpgradeCode all the time. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 11:18 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning As I had described in my other emails, I am in a situation where our upgrades are really just an install of another version. They need to exist side-by-side. But I need to remove the warning that is brought up that I don't have an upgrade code, and the upgrade code can't have the * value. Christoph -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
This statement is not true: Having the same UpgradeCode for 2 installers causes the installer to initiate an upgrade instead of an additional installation. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 11:33 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Having the same UpgradeCode for 2 installers causes the installer to initiate an upgrade instead of an additional installation. I want a new UpgradeCode each build, so that no 2 packages will have the same UpgradeCode, allowing us to install the multiple versions. If there is a better way to do this, I am open to it. Christoph -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
You can see my latest email. I thought about that after I emailed it, and tested it out. I realize now you need the MajorUpgrade element for it to work. Thank you for your help (everyone who responded), Christoph -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: Tuesday, May 26, 2015 3:04 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning This statement is not true: Having the same UpgradeCode for 2 installers causes the installer to initiate an upgrade instead of an additional installation. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 11:33 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Having the same UpgradeCode for 2 installers causes the installer to initiate an upgrade instead of an additional installation. I want a new UpgradeCode each build, so that no 2 packages will have the same UpgradeCode, allowing us to install the multiple versions. If there is a better way to do this, I am open to it. Christoph -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
Yeah, ships passing in the night. smile/ ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 12:07 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning You can see my latest email. I thought about that after I emailed it, and tested it out. I realize now you need the MajorUpgrade element for it to work. Thank you for your help (everyone who responded), Christoph -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
Don't add a MajorUpgrade element. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 9:24 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning I'm understanding now that I can use the MajorUpgrade element while providing a UpgradeCode to achieve what I need. I'm just not sure from the documentation yet. What attributes do I need to include for the MajorUpgrade element? I looked at the documentation and it isn't immediately clear to me. I need to still allow multiple versions of the product to be installed. They'll have the same GUIDs, though, since we can't automatically generate the GUIDs every build for the UpgradeCode. So if I say Disallow=yes for MajorUpgrade, will I still be able to have multiple versions installed? Christoph -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
I am WELL aware of the following: 1) You should always have an upgrade code, even if you don't plan on upgrading. But for this specific product, I am positive I do not want the upgrade code. We will never support an upgrade for this product, due to other incredibly obnoxious issues. Haha. Famous last words! :) (Several times we've been absolutely assured that X will _never_ happen. So we base our architecture on that. A time duration=soon/ later, we need to implement X. sigh. We (devs) now architect with the assumption that X will happen.) Seriously, just set the upgrade code. GUIDs are cheap. If you will never upgrade, nothing is lost. But if you do ... major pain averted! Dave -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
Jacob, I'm already sabotaged. The scenario is: Another team developed an InstallShield package for an msi, and a Wise package for an exe. The packages didn't even match in what they were delivering (a headache in itself). They didn't follow the installer rules. What they did, was deliver to a temp directory, then ran a custom action .bat file to copy the files to a version directory within the main directory for the product. But there's also common files between versions, so there's logic about whether to replace those or not. Anyways, it breaks all the rules about how to specify components, so the installer has no idea of what files are actually there. So there were so many installation defects, that now we had to come in to clean up their install. But we can't reuse GUIDs and their program doesn't even show up in the add/remove programs. And just to make everything more fun, you can have multiple versions of the product installed at the same time. It's causing a headache, because you can't do an upgrade, but we can't even follow normal rules of adding shared GUIDs to components between versions. We have resorted to completely removing the uninstall option if a legacy product is installed (ridiculous, right?). So I need to suppress the upgrade, because the idea of an upgrade is really just an install of a different version. If you have a way better way to go around this, please feel free to educate me. Because this is also my first WiX project, and I'm just working with what I got. Christoph -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Tuesday, May 26, 2015 11:52 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Why would you want to intentionally sabotage yourself? Provide an UpgradeCode, and just don't release any upgrades. -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Tuesday, May 26, 2015 10:33 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Provide the UpgradeCode and suppress upgrades in the MajorUpgrade element. -- John Merryweather Cooper Senior Software Engineer | Integration Development Group | Enterprise Notification Service Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 10:27 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Hiding UpgradeCode Attribute Warning The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin. I am getting the following error for my project: The Product/@UpgradeCode attribute was not found; it is strongly recommended to ensure that this product can be upgraded. I am WELL aware of the following: 1) You should always have an upgrade code, even if you don't plan on upgrading. But for this specific product, I am positive I do not want the upgrade code. We will never support an upgrade for this product, due to other incredibly obnoxious issues. 2) This is a warning, not an error. Unfortunately, for releasing we MUST specify to treat warnings as errors, so I need to mitigate this error. My question is, how do I suppress this error since it doesn't have an error code, just a message? Or is there anything to include in the code to mitigate the error? Thank you, Christoph Griesshammer GE Healthcare IT Software Engineer E: christoph.griessham...@ge.commailto:christoph.griessham...@ge.com http://www.gehealthcare.comhttp://www.gehealthcare.com/ 116 Huntington Ave Boston, MA, USA 02116-5744 GE Imagination at Work -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- One dashboard for servers
Re: [WiX-users] Hiding UpgradeCode Attribute Warning
To say that you don't' have time to do it right because the other team is too busy fixing bugs and adding features is planning to fail. If the application is using and deploying custom COM objects, reg-free is the only way you are going to be able to support multiple versions on the same machine. I would start by ignoring all of the existing installs, start fresh in a new folder. To support multiple versions, you'll need to auto-gen the UpgradeCode, and either auto-gen the component ID's, or change the paths so that the * component IDs get updated for each version. You'll also need to deploy them to a version specific installation folder. -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 11:22 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning We have most definitely considered that. But then comes the next issue. In order to make those changes, we need to make application changes. But we can't do that because the other team is so busy still fixing other defects and adding new features, that we can hardly coordinate enough time to talk about the installer, let alone talk about changing the application. Also, we have customers in the field that will be using the old version and new version on the same machine, so we can't make any changes to existing applications. Christoph -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Tuesday, May 26, 2015 12:13 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning So in your cleanup efforts, why not cut ties with the old versions completely? Put it in a new and unique folder, and handle the common files. I don't know if any of them use COM, the GAC, or if you have access or the ability to request a rebuild of the application. For COM, I'd suggest eliminating the inter-dependency of multiple versions (since it sounds like the rules of COM weren't followed for backwards compatibility) by using a manifest to do Reg-Free COM. If you need to add a manifest without rebuilding the application, mt.exe from the Windows SDK's can do that. -Original Message- From: Griesshammer, Christoph (GE Healthcare) [mailto:christoph.griessham...@ge.com] Sent: Tuesday, May 26, 2015 11:02 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Jacob, I'm already sabotaged. The scenario is: Another team developed an InstallShield package for an msi, and a Wise package for an exe. The packages didn't even match in what they were delivering (a headache in itself). They didn't follow the installer rules. What they did, was deliver to a temp directory, then ran a custom action .bat file to copy the files to a version directory within the main directory for the product. But there's also common files between versions, so there's logic about whether to replace those or not. Anyways, it breaks all the rules about how to specify components, so the installer has no idea of what files are actually there. So there were so many installation defects, that now we had to come in to clean up their install. But we can't reuse GUIDs and their program doesn't even show up in the add/remove programs. And just to make everything more fun, you can have multiple versions of the product installed at the same time. It's causing a headache, because you can't do an upgrade, but we can't even follow normal rules of adding shared GUIDs to components between versions. We have resorted to completely removing the uninstall option if a legacy product is installed (ridiculous, right?). So I need to suppress the upgrade, because the idea of an upgrade is really just an install of a different version. If you have a way better way to go around this, please feel free to educate me. Because this is also my first WiX project, and I'm just working with what I got. Christoph -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Tuesday, May 26, 2015 11:52 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Why would you want to intentionally sabotage yourself? Provide an UpgradeCode, and just don't release any upgrades. -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Tuesday, May 26, 2015 10:33 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Hiding UpgradeCode Attribute Warning Provide the UpgradeCode and suppress upgrades in the MajorUpgrade element. -- John Merryweather Cooper Senior Software Engineer | Integration Development Group | Enterprise Notification Service Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: Griesshammer
