Hi,
The idea you are giving is not working because if u specify an Id as an
ElementPath then you cannot use the Node="element" attribute of XmlConfig. So
any thing that is created is by using the method you mentioned is getting
formed as an attribute rather than being formed as an element. In case I am
getting you wrong in this please correct me and if you can could you please
send me a code snippet of what you meant.
Thanks and Regards,
Abhradeep Guha Thakurta
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2008 9:37 AM
To: Abhradeep Thakurta
Cc: Laxmi Narsimha Rao Oruganti (SQL CE); WiX-users
Subject: Re: [WiX-users] Problem in entering nodes to machine.config using
XmlConfig of Wix
Please keep wix-users on the list so everyone can participate.
Abhradeep Thakurta wrote:
In such a situation we should enter the new node inside the empty
dependentAssembly . Now my major problem is how do I define the XPath for such
a situation.
You don't. If you use the Id of the dependentAssembly XmlConfig as the
ElementPath of another XmlConfig, the XmlConfig custom action uses that
newly-created node as the parent.
--
sig://boB
http://joyofsetup.com/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
