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"/>
Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

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.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more