Hi Stefan,
I had the same problem.
A simple but unpretty solution I found was to add a second step to populate
the empty namespace attribute. e.g.
<util:XmlConfig Id="oms.webconfig.stateserver"
File="[INSTALLLOCATION]web.config"
Action="create"
Node="element"
ElementPath="//configuration/system.web"
Name="sessionState"
On="install"
Sequence="1" />
<util:XmlConfig Id="oms.webconfig.stateserver"
File="[INSTALLLOCATION]web.config"
Action="create"
Node="value"
ElementPath="//configuration/system.web/sessionState"
Name="xmlns"
On="install"
Value="http://add-your-toplevel-schema-namespace-here";
Sequence="2" />
Which results in
<sessionState xmlns="http://add-your-toplevel-schema-namespace-here"; />
Like I said, definitely not pretty, but it does allow your document to be
read in to memory by whatever consumes and validates your xml.
Rod P
Stefan Gauter wrote:
>
> When adding a new element to my web.config with XmlConfig I'll get an
> empty xmlns attribute.
>
> <util:XmlConfig Id="oms.webconfig.stateserver"
> File="[INSTALLLOCATION]web.config"
> Action="create"
> Node="element"
> ElementPath="//configuration/system.web"
> Name="sessionState"
> On="install"
> Sequence="1"
> />
>
> Resulting in:
>
> <sessionState xmlns="" />
>
>
--
View this message in context:
http://www.nabble.com/Problem-with-XMLConfig-Element-%28empty-xmlns-attribute%29-tp16747847p17274312.html
Sent from the wix-users mailing list archive at Nabble.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
