Install documentation for dotnet CLI is wrong
See original GitHub issueI’m not really sure how else to describe the issue. The blog post you link to specifically says that there needs to be a template.config\template.json
file for dotnet new --install
to work. However, that file doesn’t exist on the repo, and pointing dotnet new --install
to a clone of the repo doesn’t do anything.
Ultimately I had to find the templates here, which finally gave the correct way to install them:
dotnet new --install "VitalElement.AvalonStudio.Templates"
Is it possible to update the documentation to correct this?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:17
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Troubleshoot .NET tool usage issues
Discover the common issues when running .NET tools and possible solutions.
Read more >.NET Core executables fail if .NET Core is not installed in ...
My concern about this design is that the error message is not clear when there are some .NET Core runtime installations in C:\Program...
Read more >c# - Installed Dotnet tools give error "Could not execute ...
I'm working on an api in .net core 5 in wsl2 and I followed all the documentation to install the entity framework core...
Read more >Octo fails to install when using the .Net Core CLI - Integration
I am attempting to install Octo on to my machine using the .Net Core CLI. I've found two sets of instructions for this...
Read more >Visual Studio 2019 unable to locate .Net Core SDK
Step 1) First run dotnet --list-sdks from the command line (as in Grzegorz Smulko's answer). Take note of the greatest version number.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Can confirm what @grokys said. Clone the repo,
dotnet new -install /path/to/repo
it works.@grokys Maybe you can publish this into NuGet Gallery, so people can install and update these templates using the package name, instead of cloning the repo.