Husky.Net VS tye

I use Husky.net to hook in dotnet format on changed files.

One suggestion that I have is to set up Husky.Net. It'll allow you to ensure that dotnet format is run on every staged file. Assuming you guys are doing appropriately sized commits and PRs, your team will be able to evaluate formatting changes better by reviewing them in chunks as they come in, and not all at once in a large codebase.

https://github.com/alirezanet/Husky.Net to auto run csharpier or anything else as a pre-commit hook

Pre-commit hooks could work for this, but you will have to ensure everyone sets up the same pre-commit hook. https://github.com/typicode/husky or https://github.com/alirezanet/Husky.Net can make that easier.

System.CommandLine is the official .NET library that provides common functionality for command-line applications. This includes features like argument parsing, automatic help text generation, tab autocomplete, suggestions, corrections, sub-commands, user cancellation, and much more. Many official .NET tools are built on top of System.CommandLine, including the .NET CLI, Kiota, Tye, numerous Azure tools, and other .NET additional tools.

I though tye was a typo but it is an actual project: https://github.com/dotnet/tye

I would like to build modules, either in a modular monolith style, or in a microservice style using DAPR and/or Tye.

GitHub: https://github.com/dotnet/tye

If you like working with docker compose, you might want to take a look at https://github.com/dotnet/tye

I think it's a good option or docker compose with your services only. Maybe check out project tye. Although it seems abandoned.

Thoughts on scaffold vs Tye ?

https://github.com/dotnet/tye for starting up many services/projects and tying them all together

Docker, and check out also Tye https://github.com/dotnet/tye