Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>As the other answers say, you need to provide an XML Schema document for your custom configuration section. There's no need to add the <code>.xsd</code> schema file to some global directory; you can reference it directly from your custom section in the <code>App.config</code> file:</p> <pre><code>&lt;configuration&gt; &lt;!-- make the custom section known to .NET's configuration manager --&gt; &lt;configSections&gt; &lt;section name="customSection" type="..." /&gt; &lt;/configSections&gt; &lt;!-- your custom section --&gt; &lt;customSection xmlns="http://tempuri.org/customSection.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="customSection.xsd"&gt; ... &lt;/customSection&gt; &lt;configuration&gt; </code></pre> <p>The <code>xmlns</code> attribute is merely there to set a default namespace, so that you don't need to set it on your <code>customSection</code> element and all of its child elements. (However, do not place the <code>xmlns</code> attribute on the <code>&lt;configuration&gt;</code> element!)</p> <p>The <code>customSection.xsd</code> contains the schema that will be used by IntelliSense, for example:</p> <pre><code>&lt;xs:schema id="customSectionSchema" targetNamespace="http://tempuri.org/customSection.xsd" elementFormDefault="qualified" xmlns="http://tempuri.org/customSection.xsd" xmlns:mstns="http://tempuri.org/customSection.xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema"&gt; &lt;xs:element name="customSection"&gt; ... &lt;/xs:element&gt; &lt;/xs:schema&gt; </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload