Re: [WiX-users] Using Product Id=*
Sorry, but i am not sure what that would entail. Can you elaborate? The PowerShell scripts are required by the chocolatey infrastructure. Gary Sent from my Windows Phone From: Gabriel Ivanesmailto:g...@fastmail.net Sent: 22/02/2013 09:33 To: General discussion for Windows Installer XML toolset.mailto:wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Using Product Id=* Gary, Why not translate your powershell's script and your product's installation in one msi ? Le %:Date:, Gary Ewan Park ge...@gep13.co.uk a écrit: Hey, Thanks for replying! Perhaps I should provide some more information... I am helping out with creating an OSS project called ChocolateyGUI. This involves creating an MSI package, which is then wrapped into a nuget package, and then which is available in install from chocolatey.org. The nuget package includes both an install and uninstall PowerShell script, which are then invoked from the chocolatey “engine” when required. To that end, in order to create the uninstall script, I was hoping to include the product code in the uninstall script. However, since it sounds like the Product Code is not easily known, I am thinking that I won’t be able to use this approach. I have “got around” this by using the LocalPackage location from the registry key that is created to uninstall the package, but not sure how “reliable” this is. This does bring up another question, and was hinted at in the other response to this question: “If you plan an upgrade, why do you need ProductCode of the previous version ?” What is the best approach here? We are going to be shipping updates to the product. We are currently working on version 0.11.0, but this will be closely followed by 0.12.0. Should I fix the Product Code, and simply uninstall the previous version. If so, what is the norm when doing this? Sorry if this is naïve, but only really just getting started with creating and maintaining msi. Thanks Gary Sent from Windows Mail From: Peter Shirtcliffe Sent: 21 February 2013 10:45 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Using Product Id=* You can use the ProductCode property within the MSI. http://msdn.microsoft.com/en-gb/library/windows/desktop/aa370854%28v=vs.85%29 .aspx If by package you mean a bootstrapper or something else external to the MSI then you can open the MSI with InstEd or Orca and examine the Property table for the same property. -Original Message- From: Gary Ewan Park [mailto:ge...@gep13.co.uk] Sent: 21 February 2013 07:00 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Using Product Id=* Hello, I am still quite new to WiX, so please bear with me... I have implemented the following pattern: http://wix.sourceforge.net/manual-wix3/major_upgrade.htm I allow for ease of upgrade. However, the installation package that I am trying to create needs to know about the ProductCode, in order to pass a parameter to the msiexec to make it uninstall the app. Since I am using Id=”*”, how can I find out the correct ProductCode (i.e. GUID), in order to pass as a parameter to msiexec. Thanks Gary Sent from Windows Mail - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sincèrement, Gabriel I know no way of judging the future but by the past
Re: [WiX-users] Using Product Id=*
This is an interesting circumstance. Chocolatey is a new way of deploying software packages, sort of like apt-get on Linux. Ordinarily, upgrading software that was previously installed via an MSI is easy. You just author a major upgrade into the next MSI or you create a patch. I'm not familiar with how Chocolatey works. If it just pulls the MSI down from the Web and installs it, then the same old tricks for upgrading should work. In other words, MSI's have an innate ability to find older versions of themselves to upgrade (as long as the UpgradeCode is the same and you've authored the necessary elements for the upgrade). Automating an uninstall would require a ProductCode I think, if you need to do all of this from a PowerShell script. You can always install Orca.exe (from the Windows SDK I think: C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\Orca.msi). This allows you to inspect an MSI package, which would let you see the Property table where the ProductCode is. In other words, once you've built the MSI, inspect it to get the ProductCode. Of course, there's nothing requiring you to use an asterisk as the Product element's Id. You could just create your own GUID and use it. Change it as necessary for upgrade packages. Be interested for you to post more on this forum about Chocolatey. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-Product-Id-tp7583827p7583876.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using Product Id=*
Hello Nick, Thanks for all the info!! Yes, normally chocolatey goes off and downloads the msi/exe from the internet, and then installs it (with whatever flags are required to silence the install). A typical install PowerShell script looks like this: https://github.com/gep13/ChocolateyPackages/blob/master/calibre/tools/chocolateyInstall.ps1 https://github.com/gep13/ChocolateyPackages/blob/master/calibre/tools/chocolateyInstall.ps1 Where there is both a 32bit and 64bit download URL, and these are passed to a chocolatey helper method which does the magic. In the case of the chocolateygui package though, we are making the msi as well. As a result, we are bundling the msi into the chocolatey package. As a result, the installation script looks like this: https://github.com/chrissie1/chocolatey-Explorer/blob/master/ChocolateyPackage/chocolateyInstall.ps1 https://github.com/chrissie1/chocolatey-Explorer/blob/master/ChocolateyPackage/chocolateyInstall.ps1 And the uninstall script which I have cooked up, looks like this: https://github.com/chrissie1/chocolatey-Explorer/blob/master/ChocolateyPackage/chocolateyUninstall.ps1 https://github.com/chrissie1/chocolatey-Explorer/blob/master/ChocolateyPackage/chocolateyUninstall.ps1 When we ship a new version of the package, we would likely be looking to completely replace the old version. So, if I have understood you correctly, we would simply need to hard code a GUID for the ProductCode (always keeping the UpgradeCode the same), which would mean I could enter the Product Code directly into the uninstall script. Then, when we are creating the new version, we would need to change the ProductCode. Does that sound about right? Thanks Gary -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-Product-Id-tp7583827p7583877.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using Product Id=*
That sounds right to me. Use a MajorUpgrade element to handle the upgrade. That will replace the obsolete version and replace it with the new one. You'll just need to manually change the Product's Id (and Product version) in updated versions of the MSI. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-Product-Id-tp7583827p7583878.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using Product Id=*
Perfect! I think I can work with this then. Our build script already handles the creation of the version number, so I should be able to generate a new GUID for the ProductCode, and then use this same GUID in the uninstall script. Let me try this out, and see how I get on. Thanks! Gary -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-Product-Id-tp7583827p7583880.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using Product Id=*
So is there a different install/uninstall set of URLs for each MSI version? Just curious. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-Product-Id-tp7583827p7583881.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using Product Id=*
Hello, From what I have seen, no, typically the download url's remain the same across different versions of the application. I personally maintain the chocolatey package for an application called calibre (and have done for almost the last year) and the download url has never changed, and there have been lots of releases. Gary -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-Product-Id-tp7583827p7583883.html Sent from the wix-users mailing list archive at Nabble.com. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using Product Id=*
You can use the ProductCode property within the MSI. http://msdn.microsoft.com/en-gb/library/windows/desktop/aa370854%28v=vs.85%29 .aspx If by package you mean a bootstrapper or something else external to the MSI then you can open the MSI with InstEd or Orca and examine the Property table for the same property. -Original Message- From: Gary Ewan Park [mailto:ge...@gep13.co.uk] Sent: 21 February 2013 07:00 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Using Product Id=* Hello, I am still quite new to WiX, so please bear with me... I have implemented the following pattern: http://wix.sourceforge.net/manual-wix3/major_upgrade.htm I allow for ease of upgrade. However, the installation package that I am trying to create needs to know about the ProductCode, in order to pass a parameter to the msiexec to make it uninstall the app. Since I am using Id=”*”, how can I find out the correct ProductCode (i.e. GUID), in order to pass as a parameter to msiexec. Thanks Gary Sent from Windows Mail - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using Product Id=*
Hello, If you plan an upgrade, why do you need ProductCode of the previous version ? Le %:Date:, Gary Ewan Park ge...@gep13.co.uk a écrit: Hello, I am still quite new to WiX, so please bear with me... I have implemented the following pattern: http://wix.sourceforge.net/manual-wix3/major_upgrade.htm I allow for ease of upgrade. However, the installation package that I am trying to create needs to know about the ProductCode, in order to pass a parameter to the msiexec to make it uninstall the app. Since I am using Id=”*”, how can I find out the correct ProductCode (i.e. GUID), in order to pass as a parameter to msiexec. Thanks Gary Sent from Windows Mail -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sincèrement, Gabriel I know no way of judging the future but by the past. Patrick Henry You can never plan the future by the past. Edmund Burke -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using Product Id=*
Hey, Thanks for replying! Perhaps I should provide some more information... I am helping out with creating an OSS project called ChocolateyGUI. This involves creating an MSI package, which is then wrapped into a nuget package, and then which is available in install from chocolatey.org. The nuget package includes both an install and uninstall PowerShell script, which are then invoked from the chocolatey “engine” when required. To that end, in order to create the uninstall script, I was hoping to include the product code in the uninstall script. However, since it sounds like the Product Code is not easily known, I am thinking that I won’t be able to use this approach. I have “got around” this by using the LocalPackage location from the registry key that is created to uninstall the package, but not sure how “reliable” this is. This does bring up another question, and was hinted at in the other response to this question: “If you plan an upgrade, why do you need ProductCode of the previous version ?” What is the best approach here? We are going to be shipping updates to the product. We are currently working on version 0.11.0, but this will be closely followed by 0.12.0. Should I fix the Product Code, and simply uninstall the previous version. If so, what is the norm when doing this? Sorry if this is naïve, but only really just getting started with creating and maintaining msi. Thanks Gary Sent from Windows Mail From: Peter Shirtcliffe Sent: 21 February 2013 10:45 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Using Product Id=* You can use the ProductCode property within the MSI. http://msdn.microsoft.com/en-gb/library/windows/desktop/aa370854%28v=vs.85%29 .aspx If by package you mean a bootstrapper or something else external to the MSI then you can open the MSI with InstEd or Orca and examine the Property table for the same property. -Original Message- From: Gary Ewan Park [mailto:ge...@gep13.co.uk] Sent: 21 February 2013 07:00 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Using Product Id=* Hello, I am still quite new to WiX, so please bear with me... I have implemented the following pattern: http://wix.sourceforge.net/manual-wix3/major_upgrade.htm I allow for ease of upgrade. However, the installation package that I am trying to create needs to know about the ProductCode, in order to pass a parameter to the msiexec to make it uninstall the app. Since I am using Id=”*”, how can I find out the correct ProductCode (i.e. GUID), in order to pass as a parameter to msiexec. Thanks Gary Sent from Windows Mail - - Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Using Product Id=*
Hello, I am still quite new to WiX, so please bear with me... I have implemented the following pattern: http://wix.sourceforge.net/manual-wix3/major_upgrade.htm I allow for ease of upgrade. However, the installation package that I am trying to create needs to know about the ProductCode, in order to pass a parameter to the msiexec to make it uninstall the app. Since I am using Id=”*”, how can I find out the correct ProductCode (i.e. GUID), in order to pass as a parameter to msiexec. Thanks Gary Sent from Windows Mail -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
