Template hangs during dotnet new
See original GitHub issueWe’re having some trouble with the dotnet CLI
template generation tool.
We had a working template, but something in the process has changed. For example, when we run:
.\nuget.exe pack .\kendo-ng
dotnet new -i .\Progress.AspNetCore.SpaTemplates.0.1.1.nupkg
dotnet new kendo-ng
_Source Code _
dotnet new hangs and never completes. Since there’s no error message, and reverting to the previously working copy doesn’t help, then we have no way to troubleshoot.
Is there anything you can do to help get us on the right path?
We tried several version of NuGet.exe 3.5 -> 4.4.1 Dotnet –version 2.1.4
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
`dotnet run` hangs when trying to run any of the .NET 5 ...
I am trying to create a new project using the vue-nuxt template and I am getting an error where running dotnet run just...
Read more >Custom dotnet new CLI templates are not shown
But I can not see my custom templates in the new project window. However they are visible in the output of dotnet new...
Read more >VS freezes with "initializing templates" after adding class or ...
Every time I add a new class (eg., in c# project), I have a popup “Initializing templates” (it appears twice) and VS freezes....
Read more >Installing dotnet new template not working from NuGet ...
I have a template which is packaged and deployed to an Azure Devops NuGet Feed. I can't install this template when I use...
Read more >Unable to uninstall `dotnet new` via folder template?
After doing a dotnet new --debug:reinit to revert the templates to their freshly installed state, the issue went away. Potential issues. While ......
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
Another way to go is to performing a clean on the project before packing the nupkg. This should eliminate the need for special directive on build-artifact files. But to be really safe, you could also include the copy-only directives, in case the nupkg gets mistakenly packed with artifacts again in a future release.
I used 2.1.4. @seancpeters has done some additional investigation & will reply in a bit with additional information & proposed changes.