Then what I described should help you. Remember, properties don't persist
after the installation. So if your UI set the property and/or your
application later changed it, a simple AppSearch will `prime the pump` if you
will and cause the same data to be written back out if the component reinstalls.
BTW, have you tried `repairing` your application? I think you'll find you
have the same problem since repair reinstalls the component.
Rennie Petersen <[EMAIL PROTECTED]> wrote:
Rob and Christopher, thanks.
Rob, you say "played games like this". You seem to be implying I'm doing
something in a non-standard or non-optimal way? If so, please let me know what
a more standard way would be to do this.
The reason I do not want to change the registry entries is that these
registry entries are used by the application to store changes in the
configuration. For example, one registry entry is used to indicate the language
to be used by the running application. It is initialized to Danish or English
at install time, depending on Windows locale info or a value entered via the
UI. But later, the user may change his/her mind and specify a different
language. An install of a minor upgrade should preserve the new value rather
than re-initialize it, otherwise the users will get upset since they have to
re-change the language once again.
Maybe this is poor application design? The application should accept
installation values in one set of registry entries and save running values
elsewhere?
But if I do it that way, how should one tell the application that you really
do want it to change the values to new installation values when that is
advantageous, for example a re-install to force a change to Swedish when that
language support is added and most of the users at this site are Swedish?
Rennie
---------------------------------
From: Christopher Painter [mailto:[EMAIL PROTECTED]
Sent: 10. juni 2007 20:07
To: Rob Mensching; Rennie Petersen; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Avoiding registry entries being modified with
REINSTALL=ALL REINSTALLMODE=vos
The description of this is a Small Update. Typically when I hear of someone
not wanting to write to the registry during an upgrade it is because they are
having negative side effects from the fact that properties don't persist in the
cached MSI and they are trying to work around the symptom instead of addresing
the cause.
Rennie, am I guessing your situation correctly? Are you using [FOO] in the
Registry table and seeing some default or null value get written to the
registry during an upgrade instead of the value that was written during the
initial installation?
If so, generally you want to use an AppSearch to retrieve the value of FOO
from the registry so that if the component reinstalls, it'll be written back
out correctly to the registry.
Rob Mensching <[EMAIL PROTECTED]> wrote:
v\:* { BEHAVIOR: url(#default#VML) } o\:* { BEHAVIOR:
url(#default#VML) } w\:* { BEHAVIOR: url(#default#VML) } .shape {
BEHAVIOR: url(#default#VML) } @font-face { font-family: Cambria Math;
} @font-face { font-family: Calibri; } @font-face { font-family: Tahoma;
} @page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New
Roman","serif" } LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt;
FONT-FAMILY: "Times New Roman","serif" } DIV.MsoNormal { FONT-SIZE: 12pt;
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif" } A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99 }
SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline;
mso-style-priority: 99 } A:visited { COLOR: purple; TEXT-DECORATION:
underline; mso-style-priority: 99 } SPAN.MsoHyperlinkFollowed { COLOR:
purple; TEXT-DECORATION:
underline; mso-style-priority: 99 } P { FONT-SIZE: 12pt; MARGIN-LEFT: 0in;
MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority:
99; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto } SPAN.EmailStyle18
{ COLOR: green; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type:
personal-reply } .MsoChpDefault { FONT-SIZE: 10pt; mso-style-type:
export-only } DIV.Section1 { page: Section1 } I havent played
games like this with the Windows Installer but my understanding is that if the
Component believes it needs to be repaired (the KeyPath is being updated) then
the whole Component gets written.
You might (although I wouldnt really recommend it) be able to condition the
registry related actions.
Why do you need to not have registry stuff written?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rennie
Petersen
Sent: Friday, June 08, 2007 3:37 AM
To: Rennie Petersen; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Avoiding registry entries being modified with
REINSTALL=ALL REINSTALLMODE=vos
No answers. :-(
Of course, this is not WiX specific, but I'm wondering if someone could help
me anyway.
To elaborate, the situation is that in my MSI I have not written any <Upgrade
element, nor any <RemoveExistingProducts element.
The <Product element contains the same Version= tag (Version="4.1.1.0") and
the same UpgradeCode=guid tag as used when the prior install was done.
On the msiexec.exe command line I specify REINSTALL=ALL and
REINSTALLMODE=vos. I'm not specifying REINSTALLMODE=vomus because I do not want
the registry entries to be modified.
But the registry entries are being modified anyway.
Any idea of how I can prevent this?
Thanks.
Rennie
---------------------------------
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rennie Petersen
Sent: 6. juni 2007 19:18
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Avoiding registry entries being modified withREINSTALL=ALL
REINSTALLMODE=vos
I'm doing a reinstall, but I don't want the existing registry entries to be
modified.
So instead of specifying REINSTALLMODE=vomus I specify REINSTALLMODE=vos.
But the registry entries still get reset to the values in my MSI.
Is it possible to avoid this?
Thanks.
Rennie
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
---------------------------------
You snooze, you lose. Get messages ASAP with AutoCheck
in the all-new Yahoo! Mail Beta.
---------------------------------
Looking for a deal? Find great prices on flights and hotels with Yahoo!
FareChase.-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
