Open smoothdeveloper opened 11 months ago
Thank you for the suggestion! This is a great suggestions and we'd love to take that into consideration. However, we are also trying to avoid that there could potentially generating manifest file accidentally on unexpected locations, and you could run unexpected tools, as the side effect of creating a manifest file by default. We did take it into consideration when adding the create-manifest-if-needed
flag. @baronfel Is there any thought from you on this feature?
Adding another outcome I encounter, and reinsures me a tiny bit in my reading comprehension
For a list of locations searched, specify the "-d" option before the tool name.
$ dotnet tool install -d fsharp-analyzers
Unrecognized command or argument 'fsharp-analyzers'.
Description:
Install global or local tool. Local tools are added to manifest and restored.
... all the help
I've not been able to try it with latest rc2, but wondering if the command still fails due to no manifest, is it advertising the option implemented in #31231?
this should be the default (if --create-manifest-if-needed is still explicit opt-in as default, rather than opt out), if it is opt-out it should just go ahead and create the manifest and print the location of it when creating it.
Also, when I run this command in https://github.com/stephan-tolksdorf/fparsec/
I get:
the
-d
flag doesn't make it list anything, only a more detailed stack trace.I tried before and after removing global.json from the fparsec repository.