Re: [WiX-users] MSI upgrade remove old registries

2010-10-19 Thread Yu, Brian
Hi Nick

I've just found out about your book and I'll buy it soon

Point1) I am using WIX to write registries, an example is provided

  
...


  


...


And is then referenced in the product.wxs


...



Point2) I think I am a bit confused about major and minor/small upgrade 

 My first installer installs some files and registry
 My second installer then updates the files (90%) to new
versions
 With some addition, edition to registry
 But I expect the registry values added by first installer to
remain if I have not touched them by second installer.
 In this scenario, should I not do major upgrade? 
   My impression of what you said is that major upgrade will remove
registry values from first installer not touched by second

When I tried to do a minor upgrade, I remember I kept the
upgrade and product code the same
And I had to run from in command line with REINSTALL=ALL
REINSTALLMODE=vomus
The problem was that it puts the registry values back to what
the installer default had, but we need to have them unchanged.

Point3) Please let me know if I should do a major and minor upgrade. 
At this point, both ways don't work and I am stuck



Regards
Brian


-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com] 
Sent: 18 October 2010 17:46
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] MSI upgrade remove old registries


A major upgrade, as you probably know, will completely remove the old
version. So, if your second installer does not write to the registry, it
makes sense that the value will be removed but not replaced. You
shouldn't
change the UpgradeCode for the lifetime of the product, across all
upgrade
scenarios. 

Are you using WiX to write to the Registry? What does that code look
like
then? 

How have you got the minor upgrade set up? Is it a patch? Or a full
install?
Does it use WiX elements to write to the Registry?
-- 
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MSI-upgrad
e-remove-old-registries-tp5639349p5647762.html
Sent from the wix-users mailing list archive at Nabble.com.


--
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly 
Flex(R) Builder(TM)) enable the development of rich applications that
run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

_
This e-mail was sent to you by EASYSCREEN LIMITED (EASYSCREEN). We are 
incorporated under the laws of England and Wales (company no. 05677531 and VAT 
registration no. 872810613). Our registered office is at 155 Bishopsgate, 
London EC2M 3TQ. This e-mail and/or any attached documents may contain 
privileged and confidential information and should only be read by those 
persons to whom this e-mail is addressed. Use by other than intended recipients 
is prohibited. If you are not the addressee, you must not copy, distribute, 
disclose or use any of the information in it. If you have received it in error, 
please delete it and immediately notify the sender. EASYSCREEN reserves the 
right to monitor all e-mail messages passing through its network. As we cannot 
guarantee the genuineness, accuracy or completeness of the information 
contained in this message, the statements set forth are not legally binding.

--
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly 
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] MSI upgrade remove old registries

2010-10-18 Thread Nick Ramirez

A major upgrade, as you probably know, will completely remove the old
version. So, if your second installer does not write to the registry, it
makes sense that the value will be removed but not replaced. You shouldn't
change the UpgradeCode for the lifetime of the product, across all upgrade
scenarios. 

Are you using WiX to write to the Registry? What does that code look like
then? 

How have you got the minor upgrade set up? Is it a patch? Or a full install?
Does it use WiX elements to write to the Registry?
-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MSI-upgrade-remove-old-registries-tp5639349p5647762.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly 
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] MSI upgrade remove old registries

2010-10-15 Thread Yu, Brian
All,

 

What I want to achieve:

I'd like to do a major upgrade with old registry settings retained from
previous installer.

i.e. registry values previously installed by an older installer which
later got updated

 

I tried the following ways but still failed.

 

Example:

I have a previous install (Installer A) that populates the registry,
say:

hklm\Brian\Test : install=1

if I then change the registry manually afterwards

hklm\Brian\Test : install=2

 

Case 1) Major upgrade

If I do a major upgrade with another installer (Installer B), it removes
hklm\Brian\Test completely.

Installer B has a new packagecode and productcode but same upgradecode
compare to Installer A.

Installer B itself does not change hklm\Brian\Test

 

I then tried with a different upgrade code, this works but you end up
having multiple entries in Add/Remove Programs

 

Case 2) Minor upgrade

Do a minor upgrade with another installer (Installer C) using
REINSTALL=ALL REINSTALLMODE=vomus

Installer C itself does not change hklm\Brian\Test

 

Result

It reverts the registry back to what the previous installer (Installer
A) default is.

i.e. hklm\Brian\Test : install=1

 

Regards

Brian


_
This e-mail was sent to you by EASYSCREEN LIMITED (EASYSCREEN). We are 
incorporated under the laws of England and Wales (company no. 05677531 and VAT 
registration no. 872810613). Our registered office is at 155 Bishopsgate, 
London EC2M 3TQ. This e-mail and/or any attached documents may contain 
privileged and confidential information and should only be read by those 
persons to whom this e-mail is addressed. Use by other than intended recipients 
is prohibited. If you are not the addressee, you must not copy, distribute, 
disclose or use any of the information in it. If you have received it in error, 
please delete it and immediately notify the sender. EASYSCREEN reserves the 
right to monitor all e-mail messages passing through its network. As we cannot 
guarantee the genuineness, accuracy or completeness of the information 
contained in this message, the statements set forth are not legally binding.
--
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly 
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users