Writing XML in Visual Basic

Hi,

Can i get some help, i need to write this...

< xml version="1.0" encoding="utf-8" >

<configuration>

<appSettings>

<add key="Domain" value="VARIABLE1" />

<add key="Dir_Pilot" value="VARIABLE2" />

<add key="ModelName_1" value="GTZ Demonstration Model" />

<add key="ModelDir_1" value="VARIABLE3 />

<add key="AllowLoginInUseOverride" value="True" />

<add key="TraceTime" value="" />

<add key="ReportSleep" value="-1" />

<add key="ReportMaxPages" value="20" />

<add key="SelectorLoadOnDemand" value="300" />

<add key="ShowSystemInformation" value="True" />

<add key="Language_1" value="en" />

<add key="DefaultCulture" value="en-US" />

</appSettings>

<system.web>

<!-- DYNAMIC DEBUG COMPILATION

Set compilation debug="true" to insert debugging symbols (.pdb information)

into the compiled page. Because this creates a larger file that executes

more slowly, you should set this value to true only when debugging and to

false at all other times. For more information, refer to the documentation about

debugging ASP.NET files.

-->

<compilation defaultLanguage="vb" debug="false" />

<!-- CUSTOM ERROR MESSAGES

Set customErrors mode="On" or "RemoteOnly" to enable custom error messages, "Off" to disable.

Add <error> tags for each of the errors you want to handle.

"On" Always display custom (friendly) messages.

"Off" Always display detailed ASP.NET error information.

"RemoteOnly" Display custom (friendly) messages only to users not running

on the local Web server. This setting is recommended for security purposes, so

that you do not display application detail information to remote clients.

-->

<customErrors mode="Off" defaultRedirect="error.aspx" />

<!-- AUTHENTICATION

This section sets the authentication policies of the application. Possible modes are "Windows",

"Forms", "Passport" and "None"

"None" No authentication is performed.

"Windows" IIS performs authentication (Basic, Digest, or Integrated Windows) according to

its settings for the application. Anonymous access must be disabled in IIS.

"Forms" You provide a custom form (Web page) for users to enter their credentials, and then

you authenticate them in your application. A user credential token is stored in a cookie.

"Passport" Authentication is performed via a centralized authentication service provided

by Microsoft that offers a single logon and core profile services for member sites.

-->

<authentication mode="Forms">

<forms name=".PROPHIX_Web"

loginUrl="Login.aspx"

protection="All"

timeout="120"

path="/" />

</authentication>

 

<!-- AUTHORIZATION

This section sets the authorization policies of the application. You can allow or deny access

to application resources by user or role. Wildcards: "*" mean everyone, " " means anonymous

(unauthenticated) users.

-->

<authorization>

<!-- <allow users="*" /> -->

<deny users=" " />

<!-- <allow users="[comma separated list of users]"

roles="[comma separated list of roles]"/>

<deny users="[comma separated list of users]"

roles="[comma separated list of roles]"/>

-->

</authorization>

 

<!-- APPLICATION-LEVEL TRACE LOGGING

Application-level tracing enables trace log output for every page within an application.

Set trace enabled="true" to enable application trace logging. If pageOutput="true", the

trace information will be displayed at the bottom of each page. Otherwise, you can view the

application trace log by browsing the "trace.axd" page from your web application

root.

-->

<trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true" />

 

<!-- SESSION STATE SETTINGS

By default ASP.NET uses cookies to identify which requests belong to a particular session.

If cookies are not available, a session can be tracked by adding a session identifier to the URL.

To disable cookies, set sessionState cookieless="true".

-->

<sessionState

mode="InProc"

stateConnectionString="tcpip=127.0.0.1:42424"

sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes"

cookieless="false"

timeout="20"

/>

<!-- GLOBALIZATION

This section sets the globalization settings of the application.

-->

<globalization requestEncoding="utf-8" responseEncoding="utf-8" />

</system.web>

</configuration>

With the variables driven from text boxes.


Help help would be great.

Thanks Craig



Answer this question

Writing XML in Visual Basic

  • Beemer

    A quick way is to put the whole XML in a string like this:


    < xml version="1.0" encoding="utf-8" >
    <configuration>
    <appSettings>
    <add key="Domain" value="@AppSettingsDomain" />
    <add key="Dir_Pilot" value="@AppSettingsDir_Pilot" />
    <add key="ModelName_1" value="@AppSettingsModelName_1" />
    <add key="ModelDir_1" value="@AppSettingsModelDir_1" />
    <add key="AllowLoginInUseOverride" value="True" />

     


    And then just simple replace all @ElementName placeholders like:


    myXMLString.Replace("@AppSettingsDomain
    ", txtDomain.Text);
    myXMLString.Replace("@AppSettingsDir_Pilot", txtDirPilot.Text );
    // and so on

     


    Then just simple save the string to a textfile with the extension .xml:


    using(StreamWriter writer = new StreamWriter(@"c:\myfile.xml"))
    {
          writer.Write( myXMLString );
          writer.Close();
    }

     


    You can do it nicer but this work. When you dislike this, then write a wrapper class with all values as properties and write it with a XmlTextWriter to a file.


  • Frank H. Shaw

    Hi,

    Thanks for that, I've tried the myXMLString.Replace ("@AppSettingsDomain", txtDomain.Text) and it doesn't seem to be replacing the string. Any ideas


  • Jerry Cheng

    Sorry, my bad! How stupid of me, but i wrote it out of the head. You must use:



    myXMLString = myXMLString.Replace("@AppSettingsDomain
    ", txtDomain.Text);
    myXMLString = myXMLString.Replace("@AppSettingsDir_Pilot", txtDirPilot.Text );
    // and so on



  • Muljadi

    This is inefficient, but we replace a string from a file of 2MB large with over 750 place holders. It take's about 7ms and it's done.

    I know it can be done better, but something like this was 10 times faster to develop.



  • Alexander Prokofyev

    This method of using replace on all those things is extremely inefficient. You're creating and throwing away many many strings in this.

    What would be more ideal would be to use the xml dom to replace attribute values. You walk the tree looking for values that need setting, or just write a list of nodes that need to be modified, and call each xpath query for the ones you know about.

    If you like I can post you a code sample, but see how you go exploring that method.



  • Writing XML in Visual Basic