Re: [WiX-users] FW: Custom installation in Wix Patch

2013-08-27 Thread Swaroop Kare
Thanks Blair for your suggestion, I will revisit the code.

 -Original Message-
From: Blair Murri [mailto:os...@live.com] 
Sent: 26 August 2013 20:15
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] FW: Custom installation in Wix Patch

I finally got a chance to look, and it appears that your dialog
sequencing is a little inconsistent and pressing "Next->Next->Next" when
applying a patch appears to be changing your installation type (check
your verbose log for the sequence of property changes).
Some properties your UI uses are consumed before being created
(WIXUI_INSTALLMODE for one). I'm not sure what overall effect that is
having but it isn't good practice.
If you apply the patch with UI suppressed, does it add the features you
don't want added? I would expect not, given the WiX source code you sent
me.
Blair
Subject: RE: [WiX-users] Custom installation in Wix Patch
Date: Mon, 26 Aug 2013 10:10:50 +0100
From: swaroop.k...@ifdspercana.com
To: os...@live.com





























Hi Blair,

 

Did you get a chance to look at the source code sent
by me?

 

Thanks,







From:
Swaroop Kare 

Sent: 22 August 2013 15:54

To: 'os...@live.com'

Subject: RE: [WiX-users] Custom
installation in Wix Patch



 



I have now attached the file that gives you the
customized version of wix mondo.







From:
Swaroop Kare 

Sent: 22 August 2013 15:42

To: 'os...@live.com'

Subject: FW: [WiX-users] Custom
installation in Wix Patch



 

Hi Blair,

 

   I am sending the complete files for your reference. Hope
this may help.

 

   As part of my requirement, I have modified Complete
installation button of Wix to a server type installation and had
validations
accordingly. Not sure whether this is causing any issue.

 

Thanks,

 

 

-Original Message-

From: Blair Murri [mailto:os...@live.com] 

Sent: 22 August 2013 15:18

To: General discussion for Windows Installer XML
 toolset.

Subject: Re: [WiX-users] Custom installation in Wix Patch

 

If a typical installation shouldn't have SERVER_COMPONENTS or
EDS_SERVICE,
why do you have the following code:

 

> On click of typical installation button in wix, I have 

 

>  Order="1">1

 

that will always add SERVER_COMPONENTS to your installation?

 

When you perform a repair, you generally don't ever want to add or
remove features unless you really do want to modify the feature set you
are
installing.

 

> Date: Thu, 22 Aug 2013 10:48:57 +0100

> From: swaroop.k...@ifdspercana.com

> To: wix-users@lists.sourceforge.net

> Subject: Re: [WiX-users] Custom installation in Wix Patch

> 

> Hi Blair,

> 

>  

> 

> Here are my trimmed logs. For discussion purpose let us say my
typical

> installation has 'EDS_SERVICE,SERVER_COMPONENTS' features and
features

> 'EDS_SERVICE,SERVER_COMPONENTS' do not belong to typical
installation

> 

>  

> 

> Part1:

> 

> MSI (c) (8C:B8) [16:48:05:529]: PROPERTY CHANGE: Adding REINSTALL

> property. Its value is

> 'LIFEADMIN_COMPONENTS,SCHEDULEMANAGER_COMPONENTS'.

> 

> MSI (c) (8C:B8) [16:48:05:529]: PROPERTY CHANGE: Adding ADDLOCAL

> property. Its value is 'EDS_SERVICE,SERVER_COMPONENTS'.

> 

> MSI (c) (8C:B8) [16:48:05:529]: PROPERTY CHANGE: Adding
INSTALLLEVEL

> property. Its value is '1'.

> 

>  

> 

> Part2:

> 

> MSI (s) (28:18) [16:48:12:202]: Package name retrieved from

> configuration data: 'TestPatchBase.msi'

> 

> MSI (s) (28:18) [16:48:12:202]: Using cached product context:
machine

> assigned for product: AD60EC3DF3B458A448D1943F1021B54C

> 

> MSI (s) (28:18) [16:48:12:202]: Determined that existing product
(either

> this product or the product being upgraded with a patch) is
installed

> per-machine.

> 

> MSI (s) (28:18) [16:48:12:202]: Note: 1: 2262 2: AdminProperties
3:

> -2147287038 

> 

> MSI (s) (28:18) [16:48:12:202]: Machine policy value 'DisableMsi'
is 0

> 

> MSI (s) (28:18) [16:48:12:202]: Machine policy value

> 'AlwaysInstallElevated' is 0

> 

> MSI (s) (28:18) [16:48:12:202]: User policy value

> 'AlwaysInstallElevated' is 0

> 

> MSI (s) (28:18) [16:48:12:202]: Using cached product context:
machine

> assigned for product: AD60EC3DF3B458A448D1943F1021B54C

> 

> MSI (s) (28:18) [16:48:12:202]: Product

> {D3CE06DA-4B3F-4A85-841D-49F301125BC4} is admin assigned:
LocalSystem

> owns the publish key.

> 

> MSI (s) (28:18) [16:48:12:202]: Product

> {D3CE06DA-4B3F-4A85-841D-49F301125BC4} is managed.

> 

> MSI (s) (28:18) [16:48:12:202]: Running product

> '{D3CE06DA-4B3F-4A85-841D-49F301125BC4}' with elevated privileges:

> Product is assigned.

> 

>  

> 

> MSI (s) (28:1

[WiX-users] FW: Custom installation in Wix Patch

2013-08-26 Thread Blair Murri
I finally got a chance to look, and it appears that your dialog sequencing is a 
little inconsistent and pressing "Next->Next->Next" when applying a patch 
appears to be changing your installation type (check your verbose log for the 
sequence of property changes).
Some properties your UI uses are consumed before being created 
(WIXUI_INSTALLMODE for one). I'm not sure what overall effect that is having 
but it isn't good practice.
If you apply the patch with UI suppressed, does it add the features you don't 
want added? I would expect not, given the WiX source code you sent me.
Blair
Subject: RE: [WiX-users] Custom installation in Wix Patch
Date: Mon, 26 Aug 2013 10:10:50 +0100
From: swaroop.k...@ifdspercana.com
To: os...@live.com





























Hi Blair,

 

Did you get a chance to look at the source code sent
by me?

 

Thanks,







From:
Swaroop Kare 

Sent: 22 August 2013 15:54

To: 'os...@live.com'

Subject: RE: [WiX-users] Custom
installation in Wix Patch



 



I have now attached the file that gives you the
customized version of wix mondo.







From:
Swaroop Kare 

Sent: 22 August 2013 15:42

To: 'os...@live.com'

Subject: FW: [WiX-users] Custom
installation in Wix Patch



 

Hi Blair,

 

   I am sending the complete files for your reference. Hope
this may help.

 

   As part of my requirement, I have modified Complete
installation button of Wix to a server type installation and had validations
accordingly. Not sure whether this is causing any issue.

 

Thanks,

 

 

-Original Message-

From: Blair Murri [mailto:os...@live.com] 

Sent: 22 August 2013 15:18

To: General discussion for Windows Installer XML
 toolset.

Subject: Re: [WiX-users] Custom installation in Wix Patch

 

If a typical installation shouldn't have SERVER_COMPONENTS or EDS_SERVICE,
why do you have the following code:

 

> On click of typical installation button in wix, I have 

 

>  Order="1">1

 

that will always add SERVER_COMPONENTS to your installation?

 

When you perform a repair, you generally don't ever want to add or
remove features unless you really do want to modify the feature set you are
installing.

 

> Date: Thu, 22 Aug 2013 10:48:57 +0100

> From: swaroop.k...@ifdspercana.com

> To: wix-users@lists.sourceforge.net

> Subject: Re: [WiX-users] Custom installation in Wix Patch

> 

> Hi Blair,

> 

>  

> 

> Here are my trimmed logs. For discussion purpose let us say my
typical

> installation has 'EDS_SERVICE,SERVER_COMPONENTS' features and
features

> 'EDS_SERVICE,SERVER_COMPONENTS' do not belong to typical
installation

> 

>  

> 

> Part1:

> 

> MSI (c) (8C:B8) [16:48:05:529]: PROPERTY CHANGE: Adding REINSTALL

> property. Its value is

> 'LIFEADMIN_COMPONENTS,SCHEDULEMANAGER_COMPONENTS'.

> 

> MSI (c) (8C:B8) [16:48:05:529]: PROPERTY CHANGE: Adding ADDLOCAL

> property. Its value is 'EDS_SERVICE,SERVER_COMPONENTS'.

> 

> MSI (c) (8C:B8) [16:48:05:529]: PROPERTY CHANGE: Adding
INSTALLLEVEL

> property. Its value is '1'.

> 

>  

> 

> Part2:

> 

> MSI (s) (28:18) [16:48:12:202]: Package name retrieved from

> configuration data: 'TestPatchBase.msi'

> 

> MSI (s) (28:18) [16:48:12:202]: Using cached product context:
machine

> assigned for product: AD60EC3DF3B458A448D1943F1021B54C

> 

> MSI (s) (28:18) [16:48:12:202]: Determined that existing product
(either

> this product or the product being upgraded with a patch) is
installed

> per-machine.

> 

> MSI (s) (28:18) [16:48:12:202]: Note: 1: 2262 2: AdminProperties
3:

> -2147287038 

> 

> MSI (s) (28:18) [16:48:12:202]: Machine policy value 'DisableMsi'
is 0

> 

> MSI (s) (28:18) [16:48:12:202]: Machine policy value

> 'AlwaysInstallElevated' is 0

> 

> MSI (s) (28:18) [16:48:12:202]: User policy value

> 'AlwaysInstallElevated' is 0

> 

> MSI (s) (28:18) [16:48:12:202]: Using cached product context:
machine

> assigned for product: AD60EC3DF3B458A448D1943F1021B54C

> 

> MSI (s) (28:18) [16:48:12:202]: Product

> {D3CE06DA-4B3F-4A85-841D-49F301125BC4} is admin assigned:
LocalSystem

> owns the publish key.

> 

> MSI (s) (28:18) [16:48:12:202]: Product

> {D3CE06DA-4B3F-4A85-841D-49F301125BC4} is managed.

> 

> MSI (s) (28:18) [16:48:12:202]: Running product

> '{D3CE06DA-4B3F-4A85-841D-49F301125BC4}' with elevated privileges:

> Product is assigned.

> 

>  

> 

> MSI (s) (28:18) [16:48:12:202]: PROPERTY CHANGE: Adding ADDLOCAL

> property. Its value is 'EDS_SERVICE,SERVER_COMPONENTS'.

> 

> MSI (s) (28:18) [16:48:12:202]: PROPERTY CHANGE: Adding REINSTALL

> property. Its value is

> 'LIFEADMIN_COMPONENTS,SCHEDULEMANAGER_COMPONENTS'.

> 

>  

> 

>  

> 

> Part3:

> 

> MSI (s) (28:18) [16:48:13:014]: Doing action: InstallValidate

> 

> Action 16:48:13: InstallValidate. Validating install

> 

> Action start 16:48:13: InstallValidate.

> 

> MSI (s) (28:18) [16:48:13:014]: Feature: LIFEADMIN_COMPONENTS;

> Installed: Local;   Request: Reinstall;  
Action: Reinstall

> 

> MSI (s) (28:18) [16:48:13:014]: