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

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.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

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