Skip to main content

Enable Intellisense for your custom config sections

Start by creating an XSD file that defines the format of the xml of your config section. You can easily do this in Visual Studio by opening an XML file and choosing XML –> Create Schema from the Toolbar menu.

Imagine we have the following custom configuration

   1:  <CustomSettings name="Something">
   2:    <ApplicationName>SomethingElse</ApplicationName>
   3:  </CustomSettings >


This will result in the following schema:

 

   1:  <?xml version="1.0" encoding="utf-8"?>
   2:  <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
   3:    <xs:element name="CustomSettings">
   4:      <xs:complexType>
   5:        <xs:sequence>
   6:          <xs:element name="ApplicationName" type="xs:string" />
   7:        </xs:sequence>
   8:        <xs:attribute name="name" type="xs:string" use="required" />
   9:      </xs:complexType>
  10:    </xs:element>
  11:  </xs:schema>
 
Now we cannot use this schema directly. What’s important is the schema definition. This should be the same as the default schema Visual Studio uses. This schema can be found in the DotNetConfig.xsd file, which is the same file you should add your XSD to. 
 
   1:  <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vs="http://schemas.microsoft.com/Visual-Studio-Intellisense" elementFormDefault="qualified" attributeFormDefault="unqualified" vs:helpNamespace="http://schemas.microsoft.com/.NetConfiguration/v2.0">
   2:    <xs:element name="CustomSettings">
   3:      <xs:complexType>
   4:        <xs:sequence>
   5:          <xs:element name="ApplicationName" type="xs:string" />
   6:        </xs:sequence>
   7:        <xs:attribute name="name" type="xs:string" use="required" />
   8:      </xs:complexType>
   9:    </xs:element>
  10:  </xs:schema>
 

As a last step you can either add the XSD in the DotNetConfig.xsd file, or put it in a seperate file and include that file in the DotNetConfig.xsd file by adding the following line right after the schema declaration in DotNetConfig.xsd.

   1:  <xs:include schemaLocation="CustomSettings.xsd"/>

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.