Sandbox monorepo to try things out in the .NET ecosystem.

This repository is first organized by the broad version of .NET is being used (e.g. it distinguishes .NET Core from .NET 6 and beyond).

As with my other "sandbox" repositories, each directory here is its own, self-contained project. Look for code and documentation in those directories, to learn more.

We're dealing with Windows and at the very least Microsoft technologies, which means CRLF line endings will appear from time to time (even the dotnet CLI creates files with these, on some occasions).

What's a developer to do? Consult these helpful posts:

• How to see waht type of line endings are in a Git repository
• How to normalize working tree files
• Force LF eol in git repo and working copy

Make some variation of the following, so that new files get added to Git with the correct line endings, regardless of any particular user's Git config. Personally, I haven't found grokking the nuances of and policing everyone's autocrlf Git config to be a very productive use of my time. I'd rather the repository just set it, without requiing any user intervention.

* text=auto eol=lf

Some variety of these commands may be helpful as well.

#What line endings are in the repository?
git ls-files --eol

#Re-normalize line endings in Git index
git add --renormalize .

#Re-create files in working directory so they match the Git index
git checkout-index --force --all