Templating: dotnet new -i '{path}' 2.1.504 vs 2.2.104

Created on 28 Feb 2019  路  12Comments  路  Source: dotnet/templating

_From @TomekDex on February 19, 2019 16:27_

Hello
Are there any differences between the templates for these dotnet versions?

After upgrading to 2.2.104, this command stopped working.

It prints everything in the same way as in the previous version and doesn't add any templates to the list

_Copied from original issue: dotnet/core#2328_

3.0 triaged

Most helpful comment

I had a similar issue. I was trying to install a template from a file path, but after running the command it would only show the usage information without telling me it succeeded or failed. I assume that because it was showing the usage information that I was doing something wrong. However, after digging a bit deeper and asking on Stackoverflow, I found that it was indeed installing the template, but not showing any details about the result of the command.

I suggest that this functionality be changed to at least include a success or failure indication.

All 12 comments

_From @karelz on February 27, 2019 1:10_

@livarcocc @nguerrera can you please help route the question?

_From @livarcocc on February 27, 2019 3:24_

@vijayrkn @mlorbetske

Yeah definitely experiencing this on osx

After running the install command

dotnet new -i dist/MiniScaffold.0.14.0.nupkg

mini-scaffold does not show up in my list of dotnet templates.

$ dotnet --info
.NET Core SDK (reflecting any global.json):
 Version:   2.2.104
 Commit:    73f036d4ac

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.14
 OS Platform: Darwin
 RID:         osx.10.14-x64
 Base Path:   /usr/local/share/dotnet/sdk/2.2.104/

Host (useful for support):
  Version: 2.2.2
  Commit:  a4fd7b2c84

Any update here? Is there'a solution for now?
---- update ---

A temp solution, you can add a global.json to set your dotnet sdk version to dotnet core 2.1

for example:

{
  "sdk": {
    "version": "2.1.602"
  }
}

then exec your install script under the folder of your global.json file

dotnet new -i <Package or Folder or *.nuspec path>

Is there a plan or roadmap to fix it? @mlorbetske

This is something we鈥檙e looking at in the work we鈥檙e currently doing to enable template search and updates. cc @seancpeters

Same issue on the latest preview 3 bits (3.0.100-preview3-010431)

dotnet new -i ./mytemplate.1.0.0.nupkg

Just prints the help, tried adding --dry-run, same result.

no bin/obj/modules/dlls/etc in the package.

structure is

  • .nuspec
  • content/

    • .template.config/



      • template.json



    • mytemplate.sln

    • src/



      • various source files and projects.



Can you try running your install command with the additional flag --dev:install, so:
dotnet new -i ./mytemplate.1.0.0.nupkg --dev:install

Depending on the type of problem encountered while installing, this may give some useful diagnostics.

@seancpeters okay, gave that a go. Nothing new to report - it just shows the help.

I had a similar issue. I was trying to install a template from a file path, but after running the command it would only show the usage information without telling me it succeeded or failed. I assume that because it was showing the usage information that I was doing something wrong. However, after digging a bit deeper and asking on Stackoverflow, I found that it was indeed installing the template, but not showing any details about the result of the command.

I suggest that this functionality be changed to at least include a success or failure indication.

The issue will be fixed with https://github.com/dotnet/templating/issues/2745, when implementing that epic install-uninstall was majorly reworked.

The error messages and the result of installation will be now shown to user. If installation was not successful, the error and the reason will be shown to user.
Draft example:

> dotnet  new  -i Take.Blip.Client.Templates::0.50.10 --nuget-source https://api.nuget.org/v3/index.json
The following template sources will be installed:
  Take.Blip.Client.Templates, version: 0.50.10

Warning: Take.Blip.Client.Templates::0.50.10 is not found in NuGet feeds https://api.nuget.org/v3/index.json.
'Take.Blip.Client.Templates::0.50.10' could not be installed, the package does not exist.

If installation was successful, the list of installed templates will be shown to user:

dotnet new3 -i Microsoft.Azure.WebJobs.ItemTemplates
The following sources will be installed:
  Microsoft.Azure.WebJobs.ItemTemplates

The template source Microsoft.Azure.WebJobs.ItemTemplates::3.1.1648 was successfully installed.
The following templates were installed:
Template Name                  Short Name  Language  Tags
-----------------------------  ----------  --------  ----------------------------------------------
DurableFunctionsOrchestration  durable     [C#]      Azure Function/Durable Functions Orchestration
SendGrid                       sendgrid    [C#]      Azure Function/Ouput/SendGrid
BlobTrigger                    blob        [C#],F#   Azure Function/Trigger/Blob
CosmosDBTrigger                cosmos      [C#],F#   Azure Function/Trigger/Cosmos DB
EventGridTrigger               eventgrid   [C#]      Azure Function/Trigger/EventGrid
EventHubTrigger                eventhub    [C#],F#   Azure Function/Trigger/EventHub
HttpTrigger                    http        [C#],F#   Azure Function/Trigger/Http
SignalRTrigger                 signalr     [C#]      Azure Function/Trigger/Http/SignalR
IotHubTrigger                  iothub      [C#]      Azure Function/Trigger/IotHub
RabbitMQTrigger                rqueue      [C#]      Azure Function/Trigger/RabbitMQ Queue
ServiceBusQueueTrigger         squeue      [C#]      Azure Function/Trigger/Service Bus/Queue
ServiceBusTopicTrigger         stopic      [C#]      Azure Function/Trigger/Service Bus/Topic
QueueTrigger                   queue       [C#]      Azure Function/Trigger/Storage Queue
TimerTrigger                   timer       [C#],F#   Azure Function/Trigger/Timer

Above was implemented, closing

Was this page helpful?
0 / 5 - 0 ratings