You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried installing the template using dotnet new -i GoldenEye.WebApi.Template.SimpleDDD but couldn't get it to be listed in the .net templates.
To be sure it is not related to my machine I tried as well on my 2nd mac. Both have .net sdk 5.0.101 installed, my 2nd machine has also all other sdks from 2.2 installed.
The template is indeed downloaded and is shown under ~/.templateengine/dotnetcli/v5.0.101/content but it's not part of the list when you do dotnet new after installing.
The exact output if the installation is
dotnet new -i GoldenEye.WebApi.Template.SimpleDDD
Determining projects to restore...
Restored /Users/NAME/.templateengine/dotnetcli/v5.0.101/scratch/restore.csproj (in 616 ms).
and then the list does not show the GoldenEye template.
I found a workaround by specifying the direct path to the downloaded nupkg file
dotnet new -i ~/.templateengine/dotnetcli/v5.0.101/content/goldeneye.webapi.template.simpleddd.5.0.0.nupkg
I have also tried to find the issue but had no luck
The text was updated successfully, but these errors were encountered:
@AndiRudi I'm aware of that issue. The template built for .NET 3.1, and it seems not to be compatible with .NET 5. It's high on my TODO list to bring it to life.
I tried installing the template using
dotnet new -i GoldenEye.WebApi.Template.SimpleDDD
but couldn't get it to be listed in the .net templates.To be sure it is not related to my machine I tried as well on my 2nd mac. Both have .net sdk 5.0.101 installed, my 2nd machine has also all other sdks from 2.2 installed.
The template is indeed downloaded and is shown under
~/.templateengine/dotnetcli/v5.0.101/content
but it's not part of the list when you dodotnet new
after installing.The exact output if the installation is
and then the list does not show the GoldenEye template.
I found a workaround by specifying the direct path to the downloaded nupkg file
I have also tried to find the issue but had no luck
The text was updated successfully, but these errors were encountered: