Skip to main content

Generate C# code from a JSON schema - Part II

Yesterday I shared how to create your C# data contracts from an available JSON schema. In that post I demonstrated Quicktype as a way to generate those contracts.

There was only one disadvantage when using Quicktype; it only supports Newtonsoft.Json. Today I want to have a look at an alternative that does have support for System.Text.Json.

Introducing NJsonSchema

After looking around on Github I found NJsonSchema for .NET:

NJsonSchema is a .NET library to read, generate and validate JSON Schema draft v4+ schemas. The library can read a schema from a file or string and validate JSON data against it. A schema can also be generated from an existing .NET class. With the code generation APIs you can generate C# and TypeScript classes or interfaces from a schema.

It offers multiple features:

  • Read existing JSON Schemas and validate JSON data
  • Generate JSON Schema from an existing .NET type
  • Generate JSON Schema from sample JSON data
  • Generate C# and TypeScript code from JSON Schema (That’s the one we are looking for!)

Generate C# data contracts using NJsonSchema

We can use the NJsonSchema  for .NET online on Apimundo.com:

Paste our JsonSchema:

Update the C# Generator Settings to use System.Text.Json. Therefore change the JsonLibrary property to SystemTextJson:

And click on Generate Code to generate our data contracts:

You can also write the generation logic yourself.

Therefore create a console application and add the following NuGet reference.

dotnet add NJsonSchema.CodeGeneration.CSharp

Add the following code:

Run the project to generate the data contracts and write them to a file.

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

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.

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’: ...