Sdk: `dotnet new tool-manifest` will put dotnet-tools.json under .config folder

[wli3]

Open this issue for feedback. We hope to use the convention of .config folder to avoid the clutter of config file under the repo root. Start from local tools manifest

[wli3]

related https://github.com/dotnet/templating/pull/1714

[KathleenDollard]

Local tools for dotnet will be manifest based, and will thus add the file dotnet-tools.json as one more configuration file in your repo!

I don't know about you, but it feels very messy to have key configuration files scattered among the actual files of your project, or among other files in the repo root.

To avoid proliferating files in these locations, we plan to put the tool-manifest file into a subdirectory named ".config"

We stressed about this name. It would be more specific to follow Git's lead and make it .dotnet-config or similar.

But it seems like such a good idea to have a place tools can optionally put their configuration files, whether or not they are dotnet specific. This feels like a step toward ending the file (or folder) proliferation.

We're looking for your thoughts on this question!

[dasMulli]

Showed off local tools at a meetup yesterday. Overall feedback quite good, except for dotnet tool run being quite verbose but consensus was that it's better for CI/CD usage.

BUT: valid question was: "Are other things moving to the .config folder as well?"

The person asking this question hoped that all the Nuget.config, Directory.Build.config, global.json etc. could all go into a .config folder to help clean up repositories.

I agree that having a .config folder ONLY for the tools manifest is quite weird if the rest of the ecosystem doesn't have that concept.

[wli3]

This is an issue asking for feedback. Now close since it has been a while