[WiX-users] VS setup project - WiX 3.0 conversion
I am just starting with WiX 3.0. As an exercise I converted one of our simple VS 2008 setup projects to WiX 3.0 and have two questions so far: 1. How do I make the new installer uninstall the previous version of the product? Is it just a matter of setting UpgradeCode? 2. How can I use Product element's Version attribute in the script? Something like this: Product Id=... Name=... Language=1033 Version=1.0.0.0 ... RegistryKey Key=Version / /Product I guess I can define a property, but is there a better way? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VS setup project - WiX 3.0 conversion
For #1 I keep forgetting that's one of the topics on my list to add to the docs. In the mean time you can read Alex's blog entry which is how I got it working: http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspx. For #2, we have this set up as a WiX preprocessor variable. Somewhere in your file put ?define myVersion=1.0.0.0?. Then wherever you want to refer to it use $(var.MyVersion). Neil From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Alex Ivanoff [EMAIL PROTECTED] Sent: Wednesday, June 25, 2008 8:04 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] VS setup project - WiX 3.0 conversion I am just starting with WiX 3.0. As an exercise I converted one of our simple VS 2008 setup projects to WiX 3.0 and have two questions so far: 1. How do I make the new installer uninstall the previous version of the product? Is it just a matter of setting UpgradeCode? 2. How can I use Product element's Version attribute in the script? Something like this: Product Id=... Name=... Language=1033 Version=1.0.0.0 ... RegistryKey Key=Version / /Product I guess I can define a property, but is there a better way? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VS setup project - WiX 3.0 conversion
It worked, thank you. But now I have another problem. Lets say I have version 1 of product: ?define ProductVersion=1.0.0.0 ? RegistryKey Key=$(var.ProductVersion) Now I am doing version 1.1: ?define ProductVersion=1.1.0.0 ? RegistryKey Key=$(var.ProductVersion) If I do upgrade from 1.0 to 1.1 the registry key 1.1.0.0 is created, but 1.0.0.0 does not get deleted. How do I fix this? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns Sent: Wednesday, June 25, 2008 10:15 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion For #1 I keep forgetting that's one of the topics on my list to add to the docs. In the mean time you can read Alex's blog entry which is how I got it working: http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-par t-8-major-upgrade.aspx. For #2, we have this set up as a WiX preprocessor variable. Somewhere in your file put ?define myVersion=1.0.0.0?. Then wherever you want to refer to it use $(var.MyVersion). Neil From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Alex Ivanoff [EMAIL PROTECTED] Sent: Wednesday, June 25, 2008 8:04 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] VS setup project - WiX 3.0 conversion I am just starting with WiX 3.0. As an exercise I converted one of our simple VS 2008 setup projects to WiX 3.0 and have two questions so far: 1. How do I make the new installer uninstall the previous version of the product? Is it just a matter of setting UpgradeCode? 2. How can I use Product element's Version attribute in the script? Something like this: Product Id=... Name=... Language=1033 Version=1.0.0.0 ... RegistryKey Key=Version / /Product I guess I can define a property, but is there a better way? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VS setup project - WiX 3.0 conversion
You need 'createAndRemoveOnUninstall' as the action for your key. I'm not sure what the attribute is and I don't have a WiX project open right now, but I'm sure somebody else will chime in or you can figure it out yourself... Kelly Alex Ivanoff [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 06/25/2008 12:33 PM Please respond to General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net To General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net cc Subject Re: [WiX-users] VS setup project - WiX 3.0 conversion It worked, thank you. But now I have another problem. Lets say I have version 1 of product: ?define ProductVersion=1.0.0.0 ? RegistryKey Key=$(var.ProductVersion) Now I am doing version 1.1: ?define ProductVersion=1.1.0.0 ? RegistryKey Key=$(var.ProductVersion) If I do upgrade from 1.0 to 1.1 the registry key 1.1.0.0 is created, but 1.0.0.0 does not get deleted. How do I fix this? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns Sent: Wednesday, June 25, 2008 10:15 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion For #1 I keep forgetting that's one of the topics on my list to add to the docs. In the mean time you can read Alex's blog entry which is how I got it working: http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-par t-8-major-upgrade.aspx. For #2, we have this set up as a WiX preprocessor variable. Somewhere in your file put ?define myVersion=1.0.0.0?. Then wherever you want to refer to it use $(var.MyVersion). Neil From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Alex Ivanoff [EMAIL PROTECTED] Sent: Wednesday, June 25, 2008 8:04 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] VS setup project - WiX 3.0 conversion I am just starting with WiX 3.0. As an exercise I converted one of our simple VS 2008 setup projects to WiX 3.0 and have two questions so far: 1. How do I make the new installer uninstall the previous version of the product? Is it just a matter of setting UpgradeCode? 2. How can I use Product element's Version attribute in the script? Something like this: Product Id=... Name=... Language=1033 Version=1.0.0.0 ... RegistryKey Key=Version / /Product I guess I can define a property, but is there a better way? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ** This communication is intended solely for the addressee and is confidential. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Unless indicated to the contrary: it does not constitute professional advice or opinions upon which reliance may be made by the addressee or any other party, and it should be considered to be a work in progress. Unless otherwise noted in this email or its attachments, this communication does not form a Statement of Actuarial Opinion under American Academy of Actuaries guidelines. ** - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VS setup project - WiX 3.0 conversion
Take a look at the RegistryKey element in the WiX documentation. You can specify the Action attribute and set it to createAndRemoveOnUninstall. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Ivanoff Sent: Wednesday, June 25, 2008 12:33 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion It worked, thank you. But now I have another problem. Lets say I have version 1 of product: ?define ProductVersion=1.0.0.0 ? RegistryKey Key=$(var.ProductVersion) Now I am doing version 1.1: ?define ProductVersion=1.1.0.0 ? RegistryKey Key=$(var.ProductVersion) If I do upgrade from 1.0 to 1.1 the registry key 1.1.0.0 is created, but 1.0.0.0 does not get deleted. How do I fix this? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns Sent: Wednesday, June 25, 2008 10:15 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion For #1 I keep forgetting that's one of the topics on my list to add to the docs. In the mean time you can read Alex's blog entry which is how I got it working: http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-par t-8-major-upgrade.aspx. For #2, we have this set up as a WiX preprocessor variable. Somewhere in your file put ?define myVersion=1.0.0.0?. Then wherever you want to refer to it use $(var.MyVersion). Neil From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Alex Ivanoff [EMAIL PROTECTED] Sent: Wednesday, June 25, 2008 8:04 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] VS setup project - WiX 3.0 conversion I am just starting with WiX 3.0. As an exercise I converted one of our simple VS 2008 setup projects to WiX 3.0 and have two questions so far: 1. How do I make the new installer uninstall the previous version of the product? Is it just a matter of setting UpgradeCode? 2. How can I use Product element's Version attribute in the script? Something like this: Product Id=... Name=... Language=1033 Version=1.0.0.0 ... RegistryKey Key=Version / /Product I guess I can define a property, but is there a better way? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VS setup project - WiX 3.0 conversion
I tried all create and createAndRemoveOnUninstall with no luck. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns Sent: Wednesday, June 25, 2008 14:46 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion Take a look at the RegistryKey element in the WiX documentation. You can specify the Action attribute and set it to createAndRemoveOnUninstall. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Ivanoff Sent: Wednesday, June 25, 2008 12:33 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion It worked, thank you. But now I have another problem. Lets say I have version 1 of product: ?define ProductVersion=1.0.0.0 ? RegistryKey Key=$(var.ProductVersion) Now I am doing version 1.1: ?define ProductVersion=1.1.0.0 ? RegistryKey Key=$(var.ProductVersion) If I do upgrade from 1.0 to 1.1 the registry key 1.1.0.0 is created, but 1.0.0.0 does not get deleted. How do I fix this? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns Sent: Wednesday, June 25, 2008 10:15 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion For #1 I keep forgetting that's one of the topics on my list to add to the docs. In the mean time you can read Alex's blog entry which is how I got it working: http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-par t-8-major-upgrade.aspx. For #2, we have this set up as a WiX preprocessor variable. Somewhere in your file put ?define myVersion=1.0.0.0?. Then wherever you want to refer to it use $(var.MyVersion). Neil From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Alex Ivanoff [EMAIL PROTECTED] Sent: Wednesday, June 25, 2008 8:04 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] VS setup project - WiX 3.0 conversion I am just starting with WiX 3.0. As an exercise I converted one of our simple VS 2008 setup projects to WiX 3.0 and have two questions so far: 1. How do I make the new installer uninstall the previous version of the product? Is it just a matter of setting UpgradeCode? 2. How can I use Product element's Version attribute in the script? Something like this: Product Id=... Name=... Language=1033 Version=1.0.0.0 ... RegistryKey Key=Version / /Product I guess I can define a property, but is there a better way? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VS setup project - WiX 3.0 conversion
#2: Why not just reference the MSI ProductVersion property? Use the [] syntax to reference properties in Registry Key, Name, or Value: RegistryKey Key=Some\Path\[ProductVersion] / -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns Sent: Wednesday, June 25, 2008 8:15 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion For #1 I keep forgetting that's one of the topics on my list to add to the docs. In the mean time you can read Alex's blog entry which is how I got it working: http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspx. For #2, we have this set up as a WiX preprocessor variable. Somewhere in your file put ?define myVersion=1.0.0.0?. Then wherever you want to refer to it use $(var.MyVersion). Neil From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Alex Ivanoff [EMAIL PROTECTED] Sent: Wednesday, June 25, 2008 8:04 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] VS setup project - WiX 3.0 conversion I am just starting with WiX 3.0. As an exercise I converted one of our simple VS 2008 setup projects to WiX 3.0 and have two questions so far: 1. How do I make the new installer uninstall the previous version of the product? Is it just a matter of setting UpgradeCode? 2. How can I use Product element's Version attribute in the script? Something like this: Product Id=... Name=... Language=1033 Version=1.0.0.0 ... RegistryKey Key=Version / /Product I guess I can define a property, but is there a better way? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VS setup project - WiX 3.0 conversion
This works, too, thank you. But it has the same problem of not deleting a key during upgrade. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Ginchereau Sent: Wednesday, June 25, 2008 14:56 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion #2: Why not just reference the MSI ProductVersion property? Use the [] syntax to reference properties in Registry Key, Name, or Value: RegistryKey Key=Some\Path\[ProductVersion] / -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns Sent: Wednesday, June 25, 2008 8:15 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion For #1 I keep forgetting that's one of the topics on my list to add to the docs. In the mean time you can read Alex's blog entry which is how I got it working: http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-par t-8-major-upgrade.aspx. For #2, we have this set up as a WiX preprocessor variable. Somewhere in your file put ?define myVersion=1.0.0.0?. Then wherever you want to refer to it use $(var.MyVersion). Neil From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Alex Ivanoff [EMAIL PROTECTED] Sent: Wednesday, June 25, 2008 8:04 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] VS setup project - WiX 3.0 conversion I am just starting with WiX 3.0. As an exercise I converted one of our simple VS 2008 setup projects to WiX 3.0 and have two questions so far: 1. How do I make the new installer uninstall the previous version of the product? Is it just a matter of setting UpgradeCode? 2. How can I use Product element's Version attribute in the script? Something like this: Product Id=... Name=... Language=1033 Version=1.0.0.0 ... RegistryKey Key=Version / /Product I guess I can define a property, but is there a better way? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VS setup project - WiX 3.0 conversion
Warning this is a guess! Do you have the RegistryKey in a component that has a different guid for each version? If not I can't see how the install would know to remove the key. Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Ivanoff Sent: 25 June 2008 21:25 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion This works, too, thank you. But it has the same problem of not deleting a key during upgrade. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Ginchereau Sent: Wednesday, June 25, 2008 14:56 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion #2: Why not just reference the MSI ProductVersion property? Use the [] syntax to reference properties in Registry Key, Name, or Value: RegistryKey Key=Some\Path\[ProductVersion] / -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns Sent: Wednesday, June 25, 2008 8:15 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion For #1 I keep forgetting that's one of the topics on my list to add to the docs. In the mean time you can read Alex's blog entry which is how I got it working: http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-par t-8-major-upgrade.aspx. For #2, we have this set up as a WiX preprocessor variable. Somewhere in your file put ?define myVersion=1.0.0.0?. Then wherever you want to refer to it use $(var.MyVersion). Neil From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Alex Ivanoff [EMAIL PROTECTED] Sent: Wednesday, June 25, 2008 8:04 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] VS setup project - WiX 3.0 conversion I am just starting with WiX 3.0. As an exercise I converted one of our simple VS 2008 setup projects to WiX 3.0 and have two questions so far: 1. How do I make the new installer uninstall the previous version of the product? Is it just a matter of setting UpgradeCode? 2. How can I use Product element's Version attribute in the script? Something like this: Product Id=... Name=... Language=1033 Version=1.0.0.0 ... RegistryKey Key=Version / /Product I guess I can define a property, but is there a better way? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VS setup project - WiX 3.0 conversion
The component key is constant. So, you are saying to put this registry key in its own component with autogenerated guid? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Sleightholm Sent: Wednesday, June 25, 2008 15:44 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion Warning this is a guess! Do you have the RegistryKey in a component that has a different guid for each version? If not I can't see how the install would know to remove the key. Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Ivanoff Sent: 25 June 2008 21:25 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion This works, too, thank you. But it has the same problem of not deleting a key during upgrade. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Ginchereau Sent: Wednesday, June 25, 2008 14:56 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion #2: Why not just reference the MSI ProductVersion property? Use the [] syntax to reference properties in Registry Key, Name, or Value: RegistryKey Key=Some\Path\[ProductVersion] / -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns Sent: Wednesday, June 25, 2008 8:15 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion For #1 I keep forgetting that's one of the topics on my list to add to the docs. In the mean time you can read Alex's blog entry which is how I got it working: http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-par t-8-major-upgrade.aspx. For #2, we have this set up as a WiX preprocessor variable. Somewhere in your file put ?define myVersion=1.0.0.0?. Then wherever you want to refer to it use $(var.MyVersion). Neil From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Alex Ivanoff [EMAIL PROTECTED] Sent: Wednesday, June 25, 2008 8:04 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] VS setup project - WiX 3.0 conversion I am just starting with WiX 3.0. As an exercise I converted one of our simple VS 2008 setup projects to WiX 3.0 and have two questions so far: 1. How do I make the new installer uninstall the previous version of the product? Is it just a matter of setting UpgradeCode? 2. How can I use Product element's Version attribute in the script? Something like this: Product Id=... Name=... Language=1033 Version=1.0.0.0 ... RegistryKey Key=Version / /Product I guess I can define a property, but is there a better way? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VS setup project - WiX 3.0 conversion
I would say if there is a new registry key then that is a new component so it needs a new guid. I wouldn't say it should be auto generated as I don't know the consequences of doing this. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Ivanoff Sent: 25 June 2008 22:06 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion The component key is constant. So, you are saying to put this registry key in its own component with autogenerated guid? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Sleightholm Sent: Wednesday, June 25, 2008 15:44 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion Warning this is a guess! Do you have the RegistryKey in a component that has a different guid for each version? If not I can't see how the install would know to remove the key. Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Ivanoff Sent: 25 June 2008 21:25 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion This works, too, thank you. But it has the same problem of not deleting a key during upgrade. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Ginchereau Sent: Wednesday, June 25, 2008 14:56 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion #2: Why not just reference the MSI ProductVersion property? Use the [] syntax to reference properties in Registry Key, Name, or Value: RegistryKey Key=Some\Path\[ProductVersion] / -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns Sent: Wednesday, June 25, 2008 8:15 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion For #1 I keep forgetting that's one of the topics on my list to add to the docs. In the mean time you can read Alex's blog entry which is how I got it working: http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-par t-8-major-upgrade.aspx. For #2, we have this set up as a WiX preprocessor variable. Somewhere in your file put ?define myVersion=1.0.0.0?. Then wherever you want to refer to it use $(var.MyVersion). Neil From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Alex Ivanoff [EMAIL PROTECTED] Sent: Wednesday, June 25, 2008 8:04 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] VS setup project - WiX 3.0 conversion I am just starting with WiX 3.0. As an exercise I converted one of our simple VS 2008 setup projects to WiX 3.0 and have two questions so far: 1. How do I make the new installer uninstall the previous version of the product? Is it just a matter of setting UpgradeCode? 2. How can I use Product element's Version attribute in the script? Something like this: Product Id=... Name=... Language=1033 Version=1.0.0.0 ... RegistryKey Key=Version / /Product I guess I can define a property, but is there a better way? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo
Re: [WiX-users] VS setup project - WiX 3.0 conversion
Well, it is not easy in my case since this registry key has reference to parent component. If I move this key to its own component I get linker errors. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Sleightholm Sent: Wednesday, June 25, 2008 16:18 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion I would say if there is a new registry key then that is a new component so it needs a new guid. I wouldn't say it should be auto generated as I don't know the consequences of doing this. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Ivanoff Sent: 25 June 2008 22:06 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion The component key is constant. So, you are saying to put this registry key in its own component with autogenerated guid? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Sleightholm Sent: Wednesday, June 25, 2008 15:44 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion Warning this is a guess! Do you have the RegistryKey in a component that has a different guid for each version? If not I can't see how the install would know to remove the key. Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Ivanoff Sent: 25 June 2008 21:25 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion This works, too, thank you. But it has the same problem of not deleting a key during upgrade. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Ginchereau Sent: Wednesday, June 25, 2008 14:56 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion #2: Why not just reference the MSI ProductVersion property? Use the [] syntax to reference properties in Registry Key, Name, or Value: RegistryKey Key=Some\Path\[ProductVersion] / -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns Sent: Wednesday, June 25, 2008 8:15 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VS setup project - WiX 3.0 conversion For #1 I keep forgetting that's one of the topics on my list to add to the docs. In the mean time you can read Alex's blog entry which is how I got it working: http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-par t-8-major-upgrade.aspx. For #2, we have this set up as a WiX preprocessor variable. Somewhere in your file put ?define myVersion=1.0.0.0?. Then wherever you want to refer to it use $(var.MyVersion). Neil From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Alex Ivanoff [EMAIL PROTECTED] Sent: Wednesday, June 25, 2008 8:04 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] VS setup project - WiX 3.0 conversion I am just starting with WiX 3.0. As an exercise I converted one of our simple VS 2008 setup projects to WiX 3.0 and have two questions so far: 1. How do I make the new installer uninstall the previous version of the product? Is it just a matter of setting UpgradeCode? 2. How can I use Product element's Version attribute in the script? Something like this: Product Id=... Name=... Language=1033 Version=1.0.0.0 ... RegistryKey Key=Version / /Product I guess I can define a property, but is there a better way? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net
