|
I am looking into different ways to handle environment
specific information in web.config files. It would seem logical if at
deployment time, my installer could determine where it is being run and update
a generic config file so that is fit for purpose for the environment it is
being run on. I wouldn’t need to create new elements exactly but just
search for partular tokens within an xml file and replace them with a value I
read in from the registry for example. The following is some sample xml from a
config file: <endpoint address="http://localhost/Configuration/ConfigurationService.svc"
binding="basicHttpBinding"
bindingConfiguration="BasicHttpBinding_IConfigurationService"
contract="Exchange.EnterpriseLibrary.Configuration.IConfigurationService"
name="BasicHttpBinding_IConfigurationService"/> I would need to replace ‘localhost’ with
something more appropriate. Is this something the XMLFile element could handle
or is there something else in WiX that could help out? |
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
