Sdk: `dotnet new manifestfile` or `dotnet tool install package id --create-new-manifest-file`

[wli3]

A way to create manifest file since we will throw when dotnet tool install cannot find a manifest file

[dasMulli]

Could a default also be to create a new manifest file at the working directory if no one is found?
Or pass an argument:

dotnet tool install foo --manifest-dir ../..

[wli3]

Could a default also be to create a new manifest file at the working directory if no one is found?

We talked about this. But the problem is if you are in a directory like /obj or /bin it won't make sense.

pass an argument

This could also work.

[dasMulli]

/obj or /bin it won't make sense.

well.. problem between keyboard and chair? 😂

alternatives: check for any known source control root, say .git or top-level .svn directory and if not found use the cwd.
You've surely discussed this as well so I'm interested in that result.

[wli3]

alternatives: check for any known source control root, say .git or top-level .svn directory and if not found use the cwd.

Yes, we discussed that. We don't want to depend on implementations of source controls. And we would have to deal with sub-model and future new source control system.

[wli3]

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

[wli3]

We went dotnet new tool-manifest