In Part 1 of this series, we created a command line program that can validate JSON files on disk, utilising System.CommandLine.DragonFruit for command line parsing and System.Text.Json for JSON validation. In this post, we’ll add the necessary code to package the console app as a .NET Tool that can be published to NuGet. Let’s jump right in! Pack as tool .NET Tools are by all accounts just regular NuGet packages, except they have special tags in their metadata.

I’ve been using .NET Tools more and more recently; once you have .NET on your system, they’re so easy to install with just one command line call and are immediately available on the path. But how does one actually create a tool and make it available? I thought I’d do a series on how to authour a tool and make it available for public installation. Let’s jump right in! Requirements The tool I’m creating is a simple JSON validator: you point it to a JSON file on disk and it returns whether the file is valid JSON or not.

I built the website JSON Validate with Blazor some time ago for the purposes of trying out Blazor, and have been updating it upon each release of Blazor since. But, I haven’t updated it in a while, and Blazor 3.2.0 Preview 2 and 3 were just released with some cool features so I thought it was about time to update. Update to 3.2.0 Preview 2 The website is currently on 3.