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

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. -

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 -- Vi

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://w

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

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

Re: [WiX-users] Using Product Id="*"

eneral 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 a écrit

Re: [WiX-users] Using Product Id="*"

om: 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/windo

Re: [WiX-users] Using Product Id="*"

‎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 "pack

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 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.h

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 t