By "moved into place" I'm referring to the default web.config & app.config
having been copied by the msi to the INSTALLDIR path where they need to reside.
Once in place I was hoping that XmlConfig allows me to update entries
configured with default settings in these files with a host specific value.
Am I interpreting things correctly in that XmlConfig doesn't allow updating an
existing node such as an AppKey or Settings entry and insteady you'd need to
deploy a web.config & app.config w/o those entries already there and then
"Create" the entries that you do want or first "Delete" the entry containing a
default setting followed by a "Create" to put the host specific entry in place?
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 29, 2008 1:44 PM
To: Robert O'Brien
Cc: 'wix-users@lists.sourceforge.net'
Subject: Re: [WiX-users] is XmlConfig intended for service deliverable cases
where you want to modify web.config & app.config settings after putting file
into place?
Robert O'Brien wrote:
is XmlConfig intended for service deliverable cases where you want to modify
web.config & app.config settings after putting file into place?
Yes, among other use cases.
On a similar front should one expect the Action="create" behavior to support
update of a default node entry already in place in the service deliverable
default web.config & app.config files that get moved into place?
What do you mean by "moved into place"? Action="create" creates new nodes; I
don't know that it lets you update an existing node.
--
sig://boB
http://joyofsetup.com/
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
