Just a reminder that if you'd like to promote continued development of JSON tech like #jsonschema#jsonpath and others in #dotnet, please consider sponsoring the #maintainers.
I've been noticing whole-machine slow downs whenever I heavily use my Dev Drive (for example, building source) that are just unacceptable.
A common example is I'll start a full build in Visual Studio and then go to type in Windows Terminal and everything I type will be delayed by multiple seconds. Even pasting will show only a few characters at a time.
I don't have anything against VS, but I just enjoy that we really make use of the available options, instead of being completely locked into everything Microsoft.
We build applications using .NET, Java and other stacks, deploy to Kubernetes on AWS, use Kafka, plus a bunch of other technologies, all working nicely together, without using everything from a single company. Love this!
The most difficult thing about this script was to get the form and the tab control to size to their contents. That doesn't happen automatically. At Powershell level, the control size appears to have a Height and Width property that can be set. That is not the case on my Powershell and Windows 10 Pro. I had to create a System.Drawing.Size object and assign that to the size property.
This is detailed, step-by-step instructions of getting this set up, with screenshots to help with commands and outcomes. An "idiot's guide" if you like, because I was that idiot.
dotnet does not appear to require a trailing backslash when you define a custom NuGet package cache path via env var NUGET_PACKAGES but Visual Studio does.