.NET single-entry repos

I've been working seriously in the .NET ecosystem for the first time ever essentially and as always I'm looking to get things into a place where all of my repos are as simple as <buildTool> build, <buildTool> test and <buildTool> publish.

On the surface the dotnet CLI seemed to be a poor fit for this and I was worried that it was going to occupy the type of space go or npm do where they're "Good Enough" at basic tasks that developers think they don't need a build tool.

Thankfully that doesn't seem to be the case. While I have a lot of issues with the .NET ecosystem there is a way to do the types of things I want and to treat the dotnet CLI as a single entrypoint.

In particular I've been impressed with how Microsoft is evolving the tooling to no longer be as dependent on Visual Studio. Not only are they making these build files more readable but they're unifying the experience across development and CI builds and they're quickly fixing both performance and ergonomic issues with creating sustainable monorepos. At each turn when I've opted in to a new feature or tried to be as up-to-date as possible the experience has been better and is directionally correct.

As this is the space I'm doing the most learning in right now I'll be writing a series of "microblogs" about the issues I've encountered and how to fix them as well as gaps we've had to fill in to make the experience more complete.