Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv)
In article [EMAIL PROTECTED], Davut Karabay [EMAIL PROTECTED] writes: When I run the new version of installer, it invokes the installed old versi= on. I don't want that happen. I want the new version installed anyway. Why? -- The Direct3D Graphics Pipeline -- DirectX 9 draft available for download http://www.xmission.com/~legalize/book/download/index.html Legalize Adulthood! http://blogs.xmission.com/legalize/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv)
Hi, When I run the new version of installer, it invokes the installed old version. I don't want that happen. I want the new version installed anyway. How can I break the link between the new and the old? I changed Product ID GUID but it didn't help. Using Launch Conditions do not help because old version is invoked. Here I am not asking msiexec /fv. My users will likely run the installer by double clicking. Thanks,Davut _ Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare! http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=wl_hotmailnews- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv)
Change the product code. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davut Karabay Sent: Thursday, November 01, 2007 1:40 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv)http://sourceforge.net/mailarchive/message.php?msg_name=E1Ing0k-0001xa-00%40xmission.xmission.com From: Richard [EMAIL PROTECTED] - 2007-11-01 19:47 In article [EMAIL PROTECTED], Davut Karabay [EMAIL PROTECTED] writes: When I run the new version of installer, it invokes the installed old versi= on. I don't want that happen. I want the new version installed anyway. Why? -- Because new version of the product is completely different from old one (apparently except the installer). Set of features, targeted platforms are different. So, it makes sense to me that new one does not invoke old cache. Specific scenario is this: --Old version is installed on XP --New version has launch conditions to install only on Vista --Try installing new version on XP (to test that it won't install) --New version invokes old cache. Launch conditions won't even run. Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare! Try now!http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=wl_hotmailnews - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv)
From the msi documentation: The ProductCode property is a unique identifier for the particular product release It sounded to me like you have a completely separate release so you should change the ProductCode property of the MSI. This is set by the Product/@Id attribute in WiX. From: Davut Karabay [mailto:[EMAIL PROTECTED] Sent: Thursday, November 01, 2007 2:31 PM To: Peter Marcu; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Hi Peter - What do you mean by changing the product code? From: [EMAIL PROTECTED] To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Date: Thu, 1 Nov 2007 13:47:35 -0700 Subject: RE: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Change the product code. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davut Karabay Sent: Thursday, November 01, 2007 1:40 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv)http://sourceforge.net/mailarchive/[EMAIL PROTECTED] From: Richard [EMAIL PROTECTED] - 2007-11-01 19:47 In article [EMAIL PROTECTED], Davut Karabay [EMAIL PROTECTED] writes: When I run the new version of installer, it invokes the installed old versi= on. I don't want that happen. I want the new version installed anyway. Why? -- Because new version of the product is completely different from old one (apparently except the installer). Set of features, targeted platforms are different. So, it makes sense to me that new one does not invoke old cache. Specific scenario is this: --Old version is installed on XP --New version has launch conditions to install only on Vista --Try installing new version on XP (to test that it won't install) --New version invokes old cache. Launch conditions won't even run. Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare! Try now!http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=wl_hotmailnews Windows Live Hotmail and Microsoft Office Outlook - together at last. Get it now!http://office.microsoft.com/en-us/outlook/HA102225181033.aspx?pid=CL100626971033 - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv)
Peter is suggesting you change your Product Id=GUID. I think you might want to also consider changing the UpgradeCode=GUID also for future ease of upgrading one product versus the other, but it really depends on what your ultimate goal is. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davut Karabay Sent: Thursday, November 01, 2007 2:31 PM To: Peter Marcu; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Hi Peter - What do you mean by changing the product code? From: [EMAIL PROTECTED] To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Date: Thu, 1 Nov 2007 13:47:35 -0700 Subject: RE: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Change the product code. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davut Karabay Sent: Thursday, November 01, 2007 1:40 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) http://sourceforge.net/mailarchive/message.php?msg_name=E1Ing0k-0001xa- [EMAIL PROTECTED] From: Richard [EMAIL PROTECTED] - 2007-11-01 19:47 In article [EMAIL PROTECTED], Davut Karabay [EMAIL PROTECTED] writes: When I run the new version of installer, it invokes the installed old versi= on. I don't want that happen. I want the new version installed anyway. Why? -- Because new version of the product is completely different from old one (apparently except the installer). Set of features, targeted platforms are different. So, it makes sense to me that new one does not invoke old cache. Specific scenario is this: --Old version is installed on XP --New version has launch conditions to install only on Vista --Try installing new version on XP (to test that it won't install) --New version invokes old cache. Launch conditions won't even run. Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare! Try now! http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=wl_hot mailnews Windows Live Hotmail and Microsoft Office Outlook - together at last. Get it now! http://office.microsoft.com/en-us/outlook/HA102225181033.aspx?pid=CL100 626971033 - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv)
That was the first thing I did, changing both product id and upgrade code. But still invokes the cached msi. I think I will give another try because everyone suggests it will work. By the way please bare with me on installers :). It is one of the things that I inherited recently. Subject: RE: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv)Date: Thu, 1 Nov 2007 14:38:33 -0700From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Peter is suggesting you change your Product Id=”GUID”. I think you might want to also consider changing the UpgradeCode=”GUID” also for future ease of upgrading one product versus the other, but it really depends on what your ultimate goal is. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davut KarabaySent: Thursday, November 01, 2007 2:31 PMTo: Peter Marcu; [EMAIL PROTECTED]: Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Hi Peter - What do you mean by changing the product code? From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; [EMAIL PROTECTED]: Thu, 1 Nov 2007 13:47:35 -0700Subject: RE: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Change the product code. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davut KarabaySent: Thursday, November 01, 2007 1:40 PMTo: [EMAIL PROTECTED]: Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) From: Richard [EMAIL PROTECTED] - 2007-11-01 19:47 In article [EMAIL PROTECTED],Davut Karabay [EMAIL PROTECTED] writes: When I run the new version of installer, it invokes the installed old versi= on. I don't want that happen. I want the new version installed anyway.Why?-- Because new version of the product is completely different from old one (apparently except the installer). Set of features, targeted platforms are different. So, it makes sense to me that new one does not invoke old cache. Specific scenario is this: --Old version is installed on XP--New version has launch conditions to install only on Vista--Try installing new version on XP (to test that it won't install)--New version invokes old cache. Launch conditions won't even run. Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare! Try now! Windows Live Hotmail and Microsoft Office Outlook – together at last. Get it now! _ Climb to the top of the charts! Play Star Shuffle: the word scramble challenge with star power. http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_oct- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv)
Note that Package ID and ProductCode are different. One is on the Package element and should always change, one is on the Product element and should change with each release. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davut Karabay Sent: Thursday, November 01, 2007 2:54 PM To: Chad Petersen; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) That was the first thing I did, changing both product id and upgrade code. But still invokes the cached msi. I think I will give another try because everyone suggests it will work. By the way please bare with me on installers :). It is one of the things that I inherited recently. Subject: RE: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Date: Thu, 1 Nov 2007 14:38:33 -0700 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Peter is suggesting you change your Product Id=GUID. I think you might want to also consider changing the UpgradeCode=GUID also for future ease of upgrading one product versus the other, but it really depends on what your ultimate goal is. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davut Karabay Sent: Thursday, November 01, 2007 2:31 PM To: Peter Marcu; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Hi Peter - What do you mean by changing the product code? From: [EMAIL PROTECTED] To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Date: Thu, 1 Nov 2007 13:47:35 -0700 Subject: RE: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Change the product code. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davut Karabay Sent: Thursday, November 01, 2007 1:40 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv)http://sourceforge.net/mailarchive/[EMAIL PROTECTED] From: Richard [EMAIL PROTECTED] - 2007-11-01 19:47 In article [EMAIL PROTECTED], Davut Karabay [EMAIL PROTECTED] writes: When I run the new version of installer, it invokes the installed old versi= on. I don't want that happen. I want the new version installed anyway. Why? -- Because new version of the product is completely different from old one (apparently except the installer). Set of features, targeted platforms are different. So, it makes sense to me that new one does not invoke old cache. Specific scenario is this: --Old version is installed on XP --New version has launch conditions to install only on Vista --Try installing new version on XP (to test that it won't install) --New version invokes old cache. Launch conditions won't even run. Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare! Try now!http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=wl_hotmailnews Windows Live Hotmail and Microsoft Office Outlook - together at last. Get it now!http://office.microsoft.com/en-us/outlook/HA102225181033.aspx?pid=CL100626971033 Climb to the top of the charts! Play Star Shuffle: the word scramble challenge with star power. Play Now!http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_oct - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv)
Rob, Peter, Blair and Chad - Thank you guys all for the help. Turns out I haven't changed Package/@Id. Now it is working as charm! Thanks a lot.Davut Date: Thu, 1 Nov 2007 15:49:24 -0700 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to prevent cached msi being invoked (not asking msiexec /fv) Can you share the before and after values for: Product/@Id Product/@UpgradeCode Package/@Id What version of the WiX toolset are you using? Davut Karabay wrote: Hi,When I run the new version of installer, it invokes the installed old version. I don't want that happen. I want the new version installed anyway. How can I break the link between the new and the old? I changed Product ID GUID but it didn't help. Using Launch Conditions do not help because old version is invoked. Here I am not asking msiexec /fv. My users will likely run the installer by double clicking.Thanks, Davut Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare! Try now! http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=wl_hotmailnews - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users _ Peek-a-boo FREE Tricks Treats for You! http://www.reallivemoms.com?ocid=TXT_TAGHMloc=us- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
