Re: [WiX-users] Why doesn't Windows Installer remove the oldversion in an upgrade?
Hi,
I found a way to solve the problem:
1. Supressing FindRelatedProducts in the InstallUISequence
InstallUISequence
FindRelatedProducts Suppress=yes /
/InstallUISequence
2. Executing FindRelatedProducts when the Next button is clicked in the
install scope dialog:
Control Id=Next Type=PushButton X=236 Y=243 Width=56 Height=17
Default=yes Text=!(loc.WixUINext)
Publish Property=ALLUSERS Value={}WixAppFolder =
PerUser/Publish
Publish Property=ALLUSERS Value=1WixAppFolder =
PerMachine/Publish
Publish Event=DoAction Value=FindRelatedProducts1/Publish
/Control
3. Disable the Back button on the following page, because
FindRelatedProducts is only executed teh first time it is called.
divo wrote:
Hi Bob,
Thanks for your answer, I totally understand that upgrading across
contexts doesn't make much sense. However, that is not my problem. Maybe I
wasn't specific enough with my explanation, so here is my scenario (pretty
much a standard setup scenario IMHO):
The setup is similar to the Advanced setup of Wix 3.0, i.e. it offers a
page where the user can select whether to install per-user or per-machine
(like in InstallScopeDlg.wxs in the UIExtension).
1. ALLUSERS is initially empty, thus per-user is the default
2. User installs per-machine by selecting the option in InstallScopeDlg
(which sets ALLUSERS = 1)
3. User updgrades to newer version, the previous version should be
removed.
4. FindRelatedProducts runs before the user makes the selection in
InstallScopeDlg, i.e. FindRelatedProducts searches for per-user
installations and ignores the per-machine installation
5. User again selects a per-machine setup in the UI.
6. The previous per-machine installation will not be removed, although the
new installation is NOT across context.
The behaviour I would like to have is that FindRelatedProducts runs AFTER
the user selected the install scope, i.e. step 4 and 5 above should be
swapped so that in step 6 the previous installation in the SAME context is
removed.
I guess that this is somehow possible but I don't know how to specify the
install sequences so that it works (and the WiX compiles).
If anyone could help me with this problem I would be really thankful,
Best Regards,
Dirk Vollmar
Bob Arnson-6 wrote:
divo wrote:
I am facing the exact same problem, i.e. FindRelatedProducts happens
long
before the user is asked to choose the installation scope in the UI.
Generally, the answer is: Don't. It relies on the user choosing the same
type of install as the prior version. Major upgrades don't work across
contexts.
--
sig://boB
http://joyofsetup.com/
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
View this message in context:
http://n2.nabble.com/Re%3A-Why-doesn%27t-Windows-Installer-remove-the-oldversion-in-an-upgrade--tp692400p1454240.html
Sent from the wix-users mailing list archive at Nabble.com.
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Why doesn't Windows Installer remove the oldversion in an upgrade?
Hi Bob, Thanks for your answer, I totally understand that upgrading across contexts doesn't make much sense. However, that is not my problem. Maybe I wasn't specific enough with my explanation, so here is my scenario (pretty much a standard setup scenario IMHO): The setup is similar to the Advanced setup of Wix 3.0, i.e. it offers a page where the user can select whether to install per-user or per-machine (like in InstallScopeDlg.wxs in the UIExtension). 1. ALLUSERS is initially empty, thus per-user is the default 2. User installs per-machine by selecting the option in InstallScopeDlg (which sets ALLUSERS = 1) 3. User updgrades to newer version, the previous version should be removed. 4. FindRelatedProducts runs before the user makes the selection in InstallScopeDlg, i.e. FindRelatedProducts searches for per-user installations and ignores the per-machine installation 5. User again selects a per-machine setup in the UI. 6. The previous per-machine installation will not be removed, although the new installation is NOT across context. The behaviour I would like to have is that FindRelatedProducts runs AFTER the user selected the install scope, i.e. step 4 and 5 above should be swapped so that in step 6 the previous installation in the SAME context is removed. I guess that this is somehow possible but I don't know how to specify the install sequences so that it works (and the WiX compiles). If anyone could help me with this problem I would be really thankful, Best Regards, Dirk Vollmar Bob Arnson-6 wrote: divo wrote: I am facing the exact same problem, i.e. FindRelatedProducts happens long before the user is asked to choose the installation scope in the UI. Generally, the answer is: Don't. It relies on the user choosing the same type of install as the prior version. Major upgrades don't work across contexts. -- sig://boB http://joyofsetup.com/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://n2.nabble.com/Re%3A-Why-doesn%27t-Windows-Installer-remove-the-oldversion-in-an-upgrade--tp692400p1453938.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Why doesn't Windows Installer remove the oldversion in an upgrade?
Hi, I am facing the exact same problem, i.e. FindRelatedProducts happens long before the user is asked to choose the installation scope in the UI. How do I solve this? I tried FindRelatedProducts After=InstallValidate /FindRelatedProducts but that simply gave an error. Which install sequence must I use to have FindRelatedProducts running after ALLUSERS has been set? Thanks for all help, divo Tony.Bjerstedt wrote: I second looking in the log for the FindRelatedProducts action. I had a similar problem recently and it came down to the ALLUSERS property not being set correctly prior to the call to FindRelatedProducts. The search found the previous per-machine install but didn't do anything with it because it was looking for a per-user version. I was setting ALLUSERS to 1 (per-machine) in a dialog [based on code dark'ed from a Visual Studio created installer] which was called long after FindRelatedProducts was executed. Since ALLUSERS was not set, FindRelatedProducts was looking for per-user versions of the product. The log noted that a per-machine version had been found, but that it was being ignored. Since all of my installations are per-machine, adding a Property element setting ALLUSERS fixed my problem. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Phil Wilson Sent: Monday, June 12, 2006 8:28 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Why doesn't Windows Installer remove the oldversion in an upgrade? Have you looked the log entries for FindRelatedProducts? They should say something about whether it found the previous version. Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Sunday, June 11, 2006 8:19 PM To: dangle123 ... Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Why doesn't Windows Installer remove the old version in an upgrade? dangle123 ... wrote: Action ended 15:21:09: InstallFinalize. Return value 1. MSI (s) (38:1C) [15:21:09:832]: Doing action: RemoveExistingProducts Action start 15:21:09: RemoveExistingProducts. Action ended 15:21:09: RemoveExistingProducts. Return value 1. Action ended 15:21:09: INSTALL. Return value 1. I'd expect to see more details in a verbose log. What you're looking for is the details around InstallValidate that indicate the action states for the product's components. What happens if you move RemoveExistingProducts to between InstallValidate and InstallInitialize? -- sig://boB http://bobs.org ___ 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 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://n2.nabble.com/Re%3A-Why-doesn%27t-Windows-Installer-remove-the-oldversion-in-an-upgrade--tp692400p1449808.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Close/restart running application on install
Hi and thanks. Yes, I could use util:CloseApplication if it was not throwing error 2762 mentioned in http://n2.nabble.com/util%3ACloseApplication---how-do-I-use-it-td732809.html. Unfortunately, this issue seems not fixed yet. I am using Wix v3.0.4513.0 Bob Arnson-6 wrote: divo wrote: Is there a similar mechanism available to close applications during installation, which automatically shows the same dialog to the user? No but in WiX v3, you can use the CloseApplication element to send close messages to given processes' windows. -- sig://boB http://joyofsetup.com/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://n2.nabble.com/Close-restart-running-application-on-install-tp1125535p1300613.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Close/restart running application on install
Hi, In my scenario I need to install an application add-in. Before installation I want to make sure that the application is not running. There are actually no files in use which need to be updated; however, the application needs to be restarted after the installation for the add-in to be loaded. MsiRMFilesInUse seems to do what I want, but I only get it to work during uninstall when there are actually files in use. Is there a similar mechanism available to close applications during installation, which automatically shows the same dialog to the user? Best Regards, divo -- View this message in context: http://n2.nabble.com/Close-restart-running-application-on-install-tp1125535p1125535.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to set CheckBox depending on installed component?
Hi, this seemed like a simple problem to me, however even after searching for a long time I could not find a solution to the following problem: In a dialog I want to change the state of a CheckBox depending on whether a certain component (in this case a file association) is already installed. Control Id=FileAssociation Type=CheckBox Property=FILE_ASSOCIATION_ODT CheckBoxValue=1 X=45 Y=110 Height=15 Width=200 Default=no Text=OpenDocument Text Documents (.odt) / Component Id=FileAssociationOdt Guid=1F338E6D-3B94-4c5b-864C-D97D26A55437 DiskId=1 Condition![CDATA[ FILE_ASSOCIATION_ODT ]]/Condition ProgId Id='openDocument.WriterDocument.1' Description='OpenDocument Text' Extension Id='odt' ContentType='application/vnd.oasis.opendocument.text' Verb Id='open' Command='Open' Target='[#MyApp.exe]' Argument='%1' / /Extension /ProgId /Component As I understood, the CheckBox state depends on the value of the property FILE_ASSOCIATION. If it is 1, the box is checked, if not, the box will be unchecked? How can I set this property? I already tried to access the value of ?FileAssociationOdt as described in http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx but no success. Any example or pointers to documentation are welcome, Thanks a lot, divo -- View this message in context: http://n2.nabble.com/How-to-set-CheckBox-depending-on-installed-component--tp1117644p1117644.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
