Re: [WiX-users] Custom installation in Wix Patch
Sorry Blair this was the typo error while explaining the scenario.
For discussion purpose let us say my typical installation has
LIFEADMIN_COMPONENTS, SCHEDULEMANAGER_COMPONENTS ' features and
Features 'EDS_SERVICE,SERVER_COMPONENTS' do not belong to typical
installation
3) Publish feature
On click of typical installation button in wix, I have
1
1
-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]: Feature: SCHEDULEMANAGER_COMPONENTS;
> Installed: Local; Request: Reinstall; Action: Reinstall
>
> MSI (s) (28:18) [16:48:13:014]: Feature: EDS_SERVICE; Installed:
Absent;
> Request: Local; Action: Local
>
> MSI (s) (28:18) [16:48:13:014]: Feature: SERVER_COMPONENTS; Installed:
> Absent; Request: Local; Action: Local
>
>
>
> Part4:
>
> Action 16:51:22: PublishFeatures. Publishing Product Features
>
> MSI (s) (28:18) [16:51:22:441]: Executing op:
>
FeaturePublish(Feature=LIFEADMIN_COMPONENTS,Parent=CLIENT_COMPONENTS,Abs
> ent=2,Component..
>
> MSI (s) (28:18) [16:51:22:441]: Executing op:
>
FeaturePu
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]: Feature: SCHEDULEMANAGER_COMPONENTS;
> Installed: Local; Request: Reinstall; Action: Reinstall
>
> MSI (s) (28:18) [16:48:13:014]: Feature: EDS_SERVICE; Installed: Absent;
> Request: Local; Action: Local
>
> MSI (s) (28:18) [16:48:13:014]: Feature: SERVER_COMPONENTS; Installed:
> Absent; Request: Local; Action: Local
>
>
>
> Part4:
>
> Action 16:51:22: PublishFeatures. Publishing Product Features
>
> MSI (s) (28:18) [16:51:22:441]: Executing op:
> FeaturePublish(Feature=LIFEADMIN_COMPONENTS,Parent=CLIENT_COMPONENTS,Abs
> ent=2,Component..
>
> MSI (s) (28:18) [16:51:22:441]: Executing op:
> FeaturePublish(Feature=SCHEDULEMANAGER_COMPONENTS,Parent=CLIENT_COMPONEN
> TS,Absent=2,Component
>
> MSI (s) (28:18) [16:51:22:473]: Executing op:
> FeaturePublish(Feature=EDS_SERVICE,,Absent=2,Component=..
>
> MSI (s) (28:18) [16:51:22:488]: Executing op:
> FeaturePublish(Feature=SERVER_COMPONENTS,,Absent=2,Component=..
>
> MSI (s) (28:18) [16:51:22:504]: Executing op:
> ActionStart(Name=PublishProduct,Description=Publishing product
> information,)
>
> Action 16:51:22: PublishProduct. Publishing product information
>
>
>
> Please let me know if you need any further information.
>
>
>
> Thanks
>
>
>
> -Original Message-
> From: Blair M
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]: Feature: SCHEDULEMANAGER_COMPONENTS;
Installed: Local; Request: Reinstall; Action: Reinstall
MSI (s) (28:18) [16:48:13:014]: Feature: EDS_SERVICE; Installed: Absent;
Request: Local; Action: Local
MSI (s) (28:18) [16:48:13:014]: Feature: SERVER_COMPONENTS; Installed:
Absent; Request: Local; Action: Local
Part4:
Action 16:51:22: PublishFeatures. Publishing Product Features
MSI (s) (28:18) [16:51:22:441]: Executing op:
FeaturePublish(Feature=LIFEADMIN_COMPONENTS,Parent=CLIENT_COMPONENTS,Abs
ent=2,Component..
MSI (s) (28:18) [16:51:22:441]: Executing op:
FeaturePublish(Feature=SCHEDULEMANAGER_COMPONENTS,Parent=CLIENT_COMPONEN
TS,Absent=2,Component
MSI (s) (28:18) [16:51:22:473]: Executing op:
FeaturePublish(Feature=EDS_SERVICE,,Absent=2,Component=..
MSI (s) (28:18) [16:51:22:488]: Executing op:
FeaturePublish(Feature=SERVER_COMPONENTS,,Absent=2,Component=..
MSI (s) (28:18) [16:51:22:504]: Executing op:
ActionStart(Name=PublishProduct,Description=Publishing product
information,)
Action 16:51:22: PublishProduct. Publishing product information
Please let me know if you need any further information.
Thanks
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: 22 August 2013 06:21
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom installation in Wix Patch
I'm interested in seeing the feature selection part of a verbose log in
both of those scenarios.
> Date: Wed, 21 Aug 2013 17:22:42 +0100
> From: swaroop.k...@ifdspercana.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Custom installation in Wix Patch
>
> Thanks for the reply. I tried few different tweeks to my wix installer
> and the patch installer installs all the components that are missing
for
> a full installation on a system that has only typical installation.
>
> When I uninstall only the patch, it only removes/updates the component
> related to the patch and leave the system with full installation
> although it is meant to have typical/limited installation.
>
> I suspect the problem lies in configuration of wix elements such as
> file, component or feature or something else. Below are some of my
code
> snippets
>
> 1)Declare component
>
>
> Source="$(var.SOURCELOCATION)\alxAnalyser.exe" KeyPath="yes" />
>
Re: [WiX-users] Custom installation in Wix Patch
I'm interested in seeing the feature selection part of a verbose log in both of those scenarios. > Date: Wed, 21 Aug 2013 17:22:42 +0100 > From: swaroop.k...@ifdspercana.com > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Custom installation in Wix Patch > > Thanks for the reply. I tried few different tweeks to my wix installer > and the patch installer installs all the components that are missing for > a full installation on a system that has only typical installation. > > When I uninstall only the patch, it only removes/updates the component > related to the patch and leave the system with full installation > although it is meant to have typical/limited installation. > > I suspect the problem lies in configuration of wix elements such as > file, component or feature or something else. Below are some of my code > snippets > > 1)Declare component > > >Source="$(var.SOURCELOCATION)\alxAnalyser.exe" KeyPath="yes" /> > > > > 2) Included in feature > Description=""> > > > > > > 3) Publish feature > On click of typical installation button in wix, I have > Order="1">1 > > Any help on this would be much appreciated. > > Thanks > > -Original Message----- > From: David Watson [mailto:dwat...@sdl.com] > Sent: 14 August 2013 11:08 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Custom installation in Wix Patch > > The latter behaviour is automatic, only installed features are patched. > > -Original Message- > From: Swaroop Kare [mailto:swaroop.k...@ifdspercana.com] > Sent: 14 August 2013 10:12 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Custom installation in Wix Patch > > In the wix major upgrade, I have a set of features and the end user has > the > option to install either typical, custom or complete features. > > > > In case of wix patch release, is it possible to give the user the same > option > of typical, custom or complete installation type. > > > > Else during the deployment can wix patch detect which features to be > deployed > based on the installation done in a system. i.e if a system is installed > with > typical installation then the wix patch update only those components > that > belong to typical installation. and if a system has a custom > installation > with only feature X then the patch update should update only those > components > that belong to feature X. > > > > Thanks > > Wix Developer > > > This email and any files transmitted with it are confidential and > intended > solely for the use of the individual or entity to which it is addressed > and > may contain information which is privileged, confidential or prohibited > from > disclosure or unauthorised use. You are hereby notified that any use, > any > form of reproduction, dissemination, copying, disclosure, modification, > distribution and/or publication of this e-mail message or its > attachments > other than by it's intended recipient is strictly prohibited by the > sender. > If you have received this email in error, please notify the system > manager by > email at ad...@ifdspercana.com Please note that any views or opinions > presented in this email are solely those of the author and do not > necessarily > represent those of the company. Finally, this email has been scanned for > the > presence of viruses. The recipient should also check this email and any > attachments for the presence of viruses. The company accepts no > liability for > any damage caused by any virus transmitted by this email > > _ > _ > > IFDS Percana Group Limited, no. 307152, is registered in Ireland at 16 > Joyce > Way, Park West Business Park, Dublin 12, Ireland. > Directors: Eugene Larmon, Patrick Concannon, William Slattery, Paul > O'Neil > (UK), Simon Hudson-Lund (UK) and Stephen Parkinson (UK) IFDS Percana > International Managed Services Limited, no. 368022, is regulated by the > Central Bank of Ireland. Registered in Ireland at 16 Joyce Way, Park > West > Business Park, Dublin 12, Ireland. > IFDS Percana International Managed Services Limited is a wholly owned > subsidiary of IFDS Percana Group Limited and provides support services > to the > life and pensions industry. > Directors: Eugene Larmon, Patrick Concannon, Stephen Parkinson (UK) and > Paul > O'Neil (UK). > www.ifdspercana.com > > _
Re: [WiX-users] Custom installation in Wix Patch
Thanks for the reply. I tried few different tweeks to my wix installer and the patch installer installs all the components that are missing for a full installation on a system that has only typical installation. When I uninstall only the patch, it only removes/updates the component related to the patch and leave the system with full installation although it is meant to have typical/limited installation. I suspect the problem lies in configuration of wix elements such as file, component or feature or something else. Below are some of my code snippets 1)Declare component 2) Included in feature 3) Publish feature On click of typical installation button in wix, I have 1 Any help on this would be much appreciated. Thanks -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: 14 August 2013 11:08 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Custom installation in Wix Patch The latter behaviour is automatic, only installed features are patched. -Original Message- From: Swaroop Kare [mailto:swaroop.k...@ifdspercana.com] Sent: 14 August 2013 10:12 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Custom installation in Wix Patch In the wix major upgrade, I have a set of features and the end user has the option to install either typical, custom or complete features. In case of wix patch release, is it possible to give the user the same option of typical, custom or complete installation type. Else during the deployment can wix patch detect which features to be deployed based on the installation done in a system. i.e if a system is installed with typical installation then the wix patch update only those components that belong to typical installation. and if a system has a custom installation with only feature X then the patch update should update only those components that belong to feature X. Thanks Wix Developer This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential or prohibited from disclosure or unauthorised use. You are hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail message or its attachments other than by it's intended recipient is strictly prohibited by the sender. If you have received this email in error, please notify the system manager by email at ad...@ifdspercana.com Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, this email has been scanned for the presence of viruses. The recipient should also check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email _ _ IFDS Percana Group Limited, no. 307152, is registered in Ireland at 16 Joyce Way, Park West Business Park, Dublin 12, Ireland. Directors: Eugene Larmon, Patrick Concannon, William Slattery, Paul O'Neil (UK), Simon Hudson-Lund (UK) and Stephen Parkinson (UK) IFDS Percana International Managed Services Limited, no. 368022, is regulated by the Central Bank of Ireland. Registered in Ireland at 16 Joyce Way, Park West Business Park, Dublin 12, Ireland. IFDS Percana International Managed Services Limited is a wholly owned subsidiary of IFDS Percana Group Limited and provides support services to the life and pensions industry. Directors: Eugene Larmon, Patrick Concannon, Stephen Parkinson (UK) and Paul O'Neil (UK). www.ifdspercana.com __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ - - Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clk trk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you adv
Re: [WiX-users] Custom installation in Wix Patch
If a patch is installed without custom actions altering feature install states the patch will only repair the features already installed that contain patched components. What happens to your feature states if you simply run "repair"? How are you running your patch? > Date: Wed, 14 Aug 2013 13:28:55 +0100 > From: swaroop.k...@ifdspercana.com > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Custom installation in Wix Patch > > Thanks David for your response. > > Wix automatic behaviour works for Typical installation and complete > installation and not for Customize installation. Looks like Wix patch > does not remember what features were installed using customize option > and it is installing all the features during the deployment. Can anyone > suggest how to fix them? > > And is there a way for the user to select option > of typical, custom or complete installation type during patch install > and for me to control custom installation during patch update? > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: 14 August 2013 11:08 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Custom installation in Wix Patch > > The latter behaviour is automatic, only installed features are patched. > > -Original Message- > From: Swaroop Kare [mailto:swaroop.k...@ifdspercana.com] > Sent: 14 August 2013 10:12 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Custom installation in Wix Patch > > In the wix major upgrade, I have a set of features and the end user has > the > option to install either typical, custom or complete features. > > > > In case of wix patch release, is it possible to give the user the same > option > of typical, custom or complete installation type. > > > > Else during the deployment can wix patch detect which features to be > deployed > based on the installation done in a system. i.e if a system is installed > with > typical installation then the wix patch update only those components > that > belong to typical installation. and if a system has a custom > installation > with only feature X then the patch update should update only those > components > that belong to feature X. > > > > Thanks > > Wix Developer > > This email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to which it is addressed and > may contain information which is privileged, confidential or prohibited from > disclosure or unauthorised use. You are hereby notified that any use, any > form of reproduction, > dissemination, copying, disclosure, modification, distribution and/or > publication of this e-mail message or its attachments other than by it's > intended recipient is strictly prohibited by the sender. If you have received > this email in error, please notify the system manager by email at > ad...@ifdspercana.com > Please note that any views or opinions presented in this email are solely > those of the author and do not necessarily represent those of the company. > Finally, this email has been scanned for the presence of viruses. The > recipient should also check this email and any attachments for the presence > of viruses. The company accepts no liability for any damage caused by any > virus transmitted by this email > __ > > IFDS Percana Group Limited, no. 307152, is registered in Ireland at 16 Joyce > Way, Park West Business Park, Dublin 12, Ireland. > Directors: Eugene Larmon, Patrick Concannon, William Slattery, Paul O'Neil > (UK), Simon Hudson-Lund (UK) and Stephen Parkinson (UK) > IFDS Percana International Managed Services Limited, no. 368022, is regulated > by the Central Bank of Ireland. Registered in Ireland at 16 Joyce Way, Park > West Business Park, Dublin 12, Ireland. > IFDS Percana International Managed Services Limited is a wholly owned > subsidiary of IFDS Percana Group Limited and provides support services to the > life and pensions industry. > Directors: Eugene Larmon, Patrick Concannon, Stephen Parkinson (UK) and Paul > O'Neil (UK). > www.ifdspercana.com > > __ > This email has been scanned by the Symantec Email Security.cloud service. > For more information please visit http://www.symanteccloud.com > __ > > -- > Get 100% visibility into Java/.NET code with AppDynamics Lite! &g
Re: [WiX-users] Custom installation in Wix Patch
Thanks David for your response. Wix automatic behaviour works for Typical installation and complete installation and not for Customize installation. Looks like Wix patch does not remember what features were installed using customize option and it is installing all the features during the deployment. Can anyone suggest how to fix them? And is there a way for the user to select option of typical, custom or complete installation type during patch install and for me to control custom installation during patch update? -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: 14 August 2013 11:08 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Custom installation in Wix Patch The latter behaviour is automatic, only installed features are patched. -Original Message- From: Swaroop Kare [mailto:swaroop.k...@ifdspercana.com] Sent: 14 August 2013 10:12 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Custom installation in Wix Patch In the wix major upgrade, I have a set of features and the end user has the option to install either typical, custom or complete features. In case of wix patch release, is it possible to give the user the same option of typical, custom or complete installation type. Else during the deployment can wix patch detect which features to be deployed based on the installation done in a system. i.e if a system is installed with typical installation then the wix patch update only those components that belong to typical installation. and if a system has a custom installation with only feature X then the patch update should update only those components that belong to feature X. Thanks Wix Developer This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential or prohibited from disclosure or unauthorised use. You are hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail message or its attachments other than by it's intended recipient is strictly prohibited by the sender. If you have received this email in error, please notify the system manager by email at ad...@ifdspercana.com Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, this email has been scanned for the presence of viruses. The recipient should also check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email __ IFDS Percana Group Limited, no. 307152, is registered in Ireland at 16 Joyce Way, Park West Business Park, Dublin 12, Ireland. Directors: Eugene Larmon, Patrick Concannon, William Slattery, Paul O'Neil (UK), Simon Hudson-Lund (UK) and Stephen Parkinson (UK) IFDS Percana International Managed Services Limited, no. 368022, is regulated by the Central Bank of Ireland. Registered in Ireland at 16 Joyce Way, Park West Business Park, Dublin 12, Ireland. IFDS Percana International Managed Services Limited is a wholly owned subsidiary of IFDS Percana Group Limited and provides support services to the life and pensions industry. Directors: Eugene Larmon, Patrick Concannon, Stephen Parkinson (UK) and Paul O'Neil (UK). www.ifdspercana.com __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom installation in Wix Patch
The latter behaviour is automatic, only installed features are patched. -Original Message- From: Swaroop Kare [mailto:swaroop.k...@ifdspercana.com] Sent: 14 August 2013 10:12 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Custom installation in Wix Patch In the wix major upgrade, I have a set of features and the end user has the option to install either typical, custom or complete features. In case of wix patch release, is it possible to give the user the same option of typical, custom or complete installation type. Else during the deployment can wix patch detect which features to be deployed based on the installation done in a system. i.e if a system is installed with typical installation then the wix patch update only those components that belong to typical installation. and if a system has a custom installation with only feature X then the patch update should update only those components that belong to feature X. Thanks Wix Developer This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential or prohibited from disclosure or unauthorised use. You are hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail message or its attachments other than by it's intended recipient is strictly prohibited by the sender. If you have received this email in error, please notify the system manager by email at ad...@ifdspercana.com Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, this email has been scanned for the presence of viruses. The recipient should also check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email _ _ IFDS Percana Group Limited, no. 307152, is registered in Ireland at 16 Joyce Way, Park West Business Park, Dublin 12, Ireland. Directors: Eugene Larmon, Patrick Concannon, William Slattery, Paul O'Neil (UK), Simon Hudson-Lund (UK) and Stephen Parkinson (UK) IFDS Percana International Managed Services Limited, no. 368022, is regulated by the Central Bank of Ireland. Registered in Ireland at 16 Joyce Way, Park West Business Park, Dublin 12, Ireland. IFDS Percana International Managed Services Limited is a wholly owned subsidiary of IFDS Percana Group Limited and provides support services to the life and pensions industry. Directors: Eugene Larmon, Patrick Concannon, Stephen Parkinson (UK) and Paul O'Neil (UK). www.ifdspercana.com __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ - - Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Custom installation in Wix Patch
In the wix major upgrade, I have a set of features and the end user has the option to install either typical, custom or complete features. In case of wix patch release, is it possible to give the user the same option of typical, custom or complete installation type. Else during the deployment can wix patch detect which features to be deployed based on the installation done in a system. i.e if a system is installed with typical installation then the wix patch update only those components that belong to typical installation. and if a system has a custom installation with only feature X then the patch update should update only those components that belong to feature X. Thanks Wix Developer This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential or prohibited from disclosure or unauthorised use. You are hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail message or its attachments other than by it's intended recipient is strictly prohibited by the sender. If you have received this email in error, please notify the system manager by email at ad...@ifdspercana.com Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, this email has been scanned for the presence of viruses. The recipient should also check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email __ IFDS Percana Group Limited, no. 307152, is registered in Ireland at 16 Joyce Way, Park West Business Park, Dublin 12, Ireland. Directors: Eugene Larmon, Patrick Concannon, William Slattery, Paul O'Neil (UK), Simon Hudson-Lund (UK) and Stephen Parkinson (UK) IFDS Percana International Managed Services Limited, no. 368022, is regulated by the Central Bank of Ireland. Registered in Ireland at 16 Joyce Way, Park West Business Park, Dublin 12, Ireland. IFDS Percana International Managed Services Limited is a wholly owned subsidiary of IFDS Percana Group Limited and provides support services to the life and pensions industry. Directors: Eugene Larmon, Patrick Concannon, Stephen Parkinson (UK) and Paul O'Neil (UK). www.ifdspercana.com __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom installation
Thanks a bunch! :-) On 4/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: VBScript? Absolutely not! Why do I say that? Because among other reasons you then place an additional dependency on the installation (the scripting runtime). True, VBScript custom actions are supported, but I think you'll find comments from people who should know (E.g. Rob Mensching – see his Blog entry in the WiX help entitled VBScript (and Jscript) MSI Custom Actions Suck – that strongly advise against it). Do it in something like C++ that you have full control over and can be built in a way that doesn't require external dependencies. You'll be thankful later. Regards, Richard -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Tal Shrestha *Sent:* Tuesday, April 24, 2007 1:06 PM *To:* WiX-Users *Subject:* Re: [WiX-users] Custom installation Thanks for your help. Do you think a safer approach would be VBScript or other easier file-manipulating language should be used instead? -- * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - 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 -- Tal Shrestha | 3dbe.com - 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
Re: [WiX-users] Custom installation
VBScript? Absolutely not! Why do I say that? Because among other reasons you then place an additional dependency on the installation (the scripting runtime). True, VBScript custom actions are supported, but I think you'll find comments from people who should know (E.g. Rob Mensching - see his Blog entry in the WiX help entitled VBScript (and Jscript) MSI Custom Actions Suck - that strongly advise against it). Do it in something like C++ that you have full control over and can be built in a way that doesn't require external dependencies. You'll be thankful later. Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tal Shrestha Sent: Tuesday, April 24, 2007 1:06 PM To: WiX-Users Subject: Re: [WiX-users] Custom installation Thanks for your help. Do you think a safer approach would be VBScript or other easier file-manipulating language should be used instead? * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - 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
Re: [WiX-users] Custom installation
Thanks for your help. Do you think a safer approach would be VBScript or other easier file-manipulating language should be used instead? On 4/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: So, what we're talking about is something like the way VB6 used to handle add-in tools… only less structured. You have my sympathy. J If the file you are appending to really is unstructured text (as opposed to something with an ini file structure, but with a txt extension), I think you only have two choices: 1) Require the end user to modify the file themselves. (This is almost certainly not an option… if for no other reason than it is seriously unfriendly to less experienced users). 2) Create a custom operation. As you observed initially, this is an area which is extremely susceptible to problems and should be approached with caution. If I had to do this, I would code it as a custom action DLL in C++, making sure of course that there are no external library dependencies. The reason for choosing a DLL instead of an EXE is just personal preference. I would probably also submit a support request to the developer / publisher of the existing application asking them to use a more structured format, ideally either ini file or XML, in subsequent releases. Good Luck! Regards, Richard -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Tal Shrestha *Sent:* Tuesday, April 24, 2007 11:26 AM *To:* WiX-Users *Subject:* Re: [WiX-users] Custom installation Yes, these are configuration files of another existing application (not mine). I must append my text to the text file in order to add this specific feature (yes, the user can choose to add it or not) -- * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - 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 -- Tal Shrestha | 3dbe.com - 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
Re: [WiX-users] Custom installation
So, what we're talking about is something like the way VB6 used to handle add-in tools... only less structured. You have my sympathy. :-) If the file you are appending to really is unstructured text (as opposed to something with an ini file structure, but with a txt extension), I think you only have two choices: 1) Require the end user to modify the file themselves. (This is almost certainly not an option... if for no other reason than it is seriously unfriendly to less experienced users). 2) Create a custom operation. As you observed initially, this is an area which is extremely susceptible to problems and should be approached with caution. If I had to do this, I would code it as a custom action DLL in C++, making sure of course that there are no external library dependencies. The reason for choosing a DLL instead of an EXE is just personal preference. I would probably also submit a support request to the developer / publisher of the existing application asking them to use a more structured format, ideally either ini file or XML, in subsequent releases. Good Luck! Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tal Shrestha Sent: Tuesday, April 24, 2007 11:26 AM To: WiX-Users Subject: Re: [WiX-users] Custom installation Yes, these are configuration files of another existing application (not mine). I must append my text to the text file in order to add this specific feature (yes, the user can choose to add it or not) * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - 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
Re: [WiX-users] Custom installation
Yes, these are configuration files of another existing application (not mine). I must append my text to the text file in order to add this specific feature (yes, the user can choose to add it or not) On 4/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Ah! So we're talking about user specific data huh. Generally speaking, users take a very dim view of an installation modifying anything they have modified, so I think that supporting rollback is probably not appropriate in this instance. My next question would be this. Why is your installation modifying files that, from what you have said so far, appear to belong to something else? (You have said that the target text file is only used by one component, but it seems the target file is not a part of that component otherwise you wouldn't be appending to it). It's fair enough if the modifications are in shared configuration files and there is no other option, but otherwise I wouldn't consider it good behavior in an installation. (I don't know what others around here think… hopefully someone else may chime in soon!) At the very least, you should probably also provide a user interface allowing them to decide if they want your installation to make those changes. I guess I'm still missing something here…. Regards, Richard -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Tal Shrestha *Sent:* Tuesday, April 24, 2007 10:55 AM *To:* WiX-Users *Subject:* Re: [WiX-users] Custom installation It's simpler than that. I have a few text lines I need to append into an existing text file. This target text file will be used only by *one* component, in my own single installation. However, once the installation is complete, the user might add (on his own, manually) more text lines - after the lines my installation added. -- * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - 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 -- Tal Shrestha | 3dbe.com - 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
Re: [WiX-users] Custom installation
Ah! So we're talking about user specific data huh. Generally speaking, users take a very dim view of an installation modifying anything they have modified, so I think that supporting rollback is probably not appropriate in this instance. My next question would be this. Why is your installation modifying files that, from what you have said so far, appear to belong to something else? (You have said that the target text file is only used by one component, but it seems the target file is not a part of that component otherwise you wouldn't be appending to it). It's fair enough if the modifications are in shared configuration files and there is no other option, but otherwise I wouldn't consider it good behavior in an installation. (I don't know what others around here think... hopefully someone else may chime in soon!) At the very least, you should probably also provide a user interface allowing them to decide if they want your installation to make those changes. I guess I'm still missing something here Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tal Shrestha Sent: Tuesday, April 24, 2007 10:55 AM To: WiX-Users Subject: Re: [WiX-users] Custom installation It's simpler than that. I have a few text lines I need to append into an existing text file. This target text file will be used only by *one* component, in my own single installation. However, once the installation is complete, the user might add (on his own, manually) more text lines - after the lines my installation added. * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - 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
Re: [WiX-users] Custom installation
It's simpler than that. I have a few text lines I need to append into an existing text file. This target text file will be used only by *one* component, in my own single installation. However, once the installation is complete, the user might add (on his own, manually) more text lines - after the lines my installation added. On 4/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Arguably, yes… if you append text to a file on installation, that text should be removed when you uninstall. If you have several installations that perform similar operations on the same file things will get really messy! Again, it may help if we know the problem you are trying to solve. For example, if you are installing several components each of which requires a chunk of text to be appended to a file then it may be appropriate to have the installation generate separate chunks of text in individual files for each component, then run a custom action to concatenate them into the final output. This way, if a component is uninstalled and the same custom action is run then the contents of the generated file should match what is required. (Having said that, in this scenario there is probably a special case where the file should be removed if all the components have been removed). Regards, Richard -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Tal Shrestha *Sent:* Tuesday, April 24, 2007 10:19 AM *To:* WiX-Users *Subject:* Re: [WiX-users] Custom installation Actually, rethinking this, this are simple text files I need to *append* text to them. (not XML or INI, just plain text files). Roll back (uninstallation) would mean the text that was appended should be stripped down, baring in mind other text might have added later on. What do you think? -- * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - 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 -- Tal Shrestha | 3dbe.com - 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
Re: [WiX-users] Custom installation
Arguably, yes... if you append text to a file on installation, that text should be removed when you uninstall. If you have several installations that perform similar operations on the same file things will get really messy! Again, it may help if we know the problem you are trying to solve. For example, if you are installing several components each of which requires a chunk of text to be appended to a file then it may be appropriate to have the installation generate separate chunks of text in individual files for each component, then run a custom action to concatenate them into the final output. This way, if a component is uninstalled and the same custom action is run then the contents of the generated file should match what is required. (Having said that, in this scenario there is probably a special case where the file should be removed if all the components have been removed). Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tal Shrestha Sent: Tuesday, April 24, 2007 10:19 AM To: WiX-Users Subject: Re: [WiX-users] Custom installation Actually, rethinking this, this are simple text files I need to *append* text to them. (not XML or INI, just plain text files). Roll back (uninstallation) would mean the text that was appended should be stripped down, baring in mind other text might have added later on. What do you think? * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - 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
Re: [WiX-users] Custom installation
Actually, rethinking this, this are simple text files I need to *append* text to them. (not XML or INI, just plain text files). Roll back (uninstallation) would mean the text that was appended should be stripped down, baring in mind other text might have added later on. What do you think? On 4/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: It depends what type of text file. If the files are XML, the wixca.wixlib includes a custom action which may accomplish what you need. If the file is an older style .ini file, then there may be support for what you need built into Microsoft Installer (see the IniFile element in the WiX help). If neither of these support what you need, I would suggest first coming back to this mailing list with a more complete description of what you need to do – it may be more sensible to do what is being asked of you a different way to avoid problems with component rules etc. If necessary (and hopefully it will not be), you will have to generate a custom operation – either in a DLL (as a custom action) or as an EXE which is executed during installation. I say that hopefully it will not be necessary because as you will know (if you are a regular reader of this group) custom actions are notoriously difficult to get 100% right when you take into account the repair and rollback requirements… and if you get them wrong you may not know it until it is too late to fix. Regards, Richard -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *barbq *Sent:* Tuesday, April 24, 2007 10:00 AM *To:* WiX-Users *Subject:* [WiX-users] Custom installation Hi, My installer is supposed to perform a custom installation procedure, such as parsing existing text files and inserting it's own text elements in these files, and also appending text to existing text files. Is there a mechasim for such actions? If not what should I use - an external DLL seems risky. Thanks -- * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - 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 -- Tal Shrestha | 3dbe.com - 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
Re: [WiX-users] Custom installation
It depends what type of text file. If the files are XML, the wixca.wixlib includes a custom action which may accomplish what you need. If the file is an older style .ini file, then there may be support for what you need built into Microsoft Installer (see the IniFile element in the WiX help). If neither of these support what you need, I would suggest first coming back to this mailing list with a more complete description of what you need to do - it may be more sensible to do what is being asked of you a different way to avoid problems with component rules etc. If necessary (and hopefully it will not be), you will have to generate a custom operation - either in a DLL (as a custom action) or as an EXE which is executed during installation. I say that hopefully it will not be necessary because as you will know (if you are a regular reader of this group) custom actions are notoriously difficult to get 100% right when you take into account the repair and rollback requirements... and if you get them wrong you may not know it until it is too late to fix. Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of barbq Sent: Tuesday, April 24, 2007 10:00 AM To: WiX-Users Subject: [WiX-users] Custom installation Hi, My installer is supposed to perform a custom installation procedure, such as parsing existing text files and inserting it's own text elements in these files, and also appending text to existing text files. Is there a mechasim for such actions? If not what should I use - an external DLL seems risky. Thanks * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - 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
[WiX-users] Custom installation
Hi, My installer is supposed to perform a custom installation procedure, such as parsing existing text files and inserting it's own text elements in these files, and also appending text to existing text files. Is there a mechasim for such actions? If not what should I use - an external DLL seems risky. Thanks - 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
