Okay I must be missing something as as I mentioned above this one did write
to the file, just did not write it correctly:

<util:XmlFile Id="ServiceInfo" Action="setValue"
ElementPath="/configuration/appSettings" Name="ServiceInfo"
Value="[LYNC_SERVER_ADDRESS]" File="[INSTALLDIR]RemoteInk.exe.config" />


When I update this to:
<util:XmlFile Id="ServiceInfo" Action="setValue"
ElementPath="/configuration/appSettings/add[\[]@key='ServiceInfo'[\]]"
Name="ServiceInfo" Value="[LYNC_SERVER_ADDRESS]"
File="[#RemoteInk.exe.config]" />

Basically the same thing except for the add[\[]@key='ServiceInfo'[\]]" and
then run it I get the 'Failed to find Node:' error. So why would adding this
give me an error unless I am missing something that can correctly read that
line...

So I only have the following at the top of my Product.wxs file:
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>

Did I have to include anything else to get this to work?

Also in your example the <add key="ServerLocation" value="" /> entry already
existed, so does that make a difference if the entry that I am trying to
create exists or not?

I'll see if I can get that example to work on my machine to verify if it
works or not.




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Which-is-best-to-use-in-my-case-XmlFile-or-XmlConfig-tp7594691p7594712.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to