diff --git a/docs/core/tools/global-tools-how-to-create.md b/docs/core/tools/global-tools-how-to-create.md index 055aecd7432f8..a955bb46455a6 100644 --- a/docs/core/tools/global-tools-how-to-create.md +++ b/docs/core/tools/global-tools-how-to-create.md @@ -13,13 +13,13 @@ This tutorial teaches you how to create and package a .NET tool. The .NET CLI le The tool that you'll create is a console application that takes a message as input and displays the message along with lines of text that create the image of a robot. -This is the first in a series of three tutorials. In this tutorial, you create and package a tool. In the next two tutorials you [use the tool as a global tool](global-tools-how-to-use.md) and [use the tool as a local tool](local-tools-how-to-use.md). +This is the first in a series of three tutorials. In this tutorial, you create and package a tool. In the next two tutorials you [use the tool as a global tool](global-tools-how-to-use.md) and [use the tool as a local tool](local-tools-how-to-use.md). The procedures for creating a tool are the same whether you use it as a global tool or as a local tool. ## Prerequisites -- [.NET Core SDK 3.1](https://dotnet.microsoft.com/download) or a later version. +- [.NET SDK 5.0](https://dotnet.microsoft.com/download) or a later version. - This tutorial and the following [tutorial for global tools](global-tools-how-to-use.md) apply to .NET Core SDK 2.1 and later versions because global tools are available starting in that version. But this tutorial assumes you have installed 3.1 or later so that you have the option of continuing on to the [local tools tutorial](local-tools-how-to-use.md). Local tools are available starting in .NET Core SDK 3.0. The procedures for creating a tool are the same whether you use it as a global tool or as a local tool. + This tutorial uses .NET SDK 5.0, but global tools are available starting in .NET Core SDK 2.1. Local tools are available starting in .NET Core SDK 3.0. - A text editor or code editor of your choice. @@ -153,7 +153,7 @@ Before you can pack and distribute the application as a tool, you need to modify `` is an optional element that specifies the command that will invoke the tool after it's installed. If this element isn't provided, the command name for the tool is the project file name without the *.csproj* extension. - `` is an optional element that determines where the NuGet package will be produced. The NuGet package is what the .NET Core CLI uses to install your tool. + `` is an optional element that determines where the NuGet package will be produced. The NuGet package is what the .NET CLI uses to install your tool. The project file now looks like the following example: @@ -163,7 +163,7 @@ Before you can pack and distribute the application as a tool, you need to modify Exe - netcoreapp3.1 + net5.0 true botsay diff --git a/docs/core/tools/local-tools-how-to-use.md b/docs/core/tools/local-tools-how-to-use.md index e082cb1adc83a..1624dd8bdebe8 100644 --- a/docs/core/tools/local-tools-how-to-use.md +++ b/docs/core/tools/local-tools-how-to-use.md @@ -2,7 +2,7 @@ title: "Tutorial: Install and use .NET local tools" description: Learn how to install and use a .NET tool as a local tool. ms.topic: tutorial -ms.date: 02/12/2020 +ms.date: 12/11/2020 --- # Tutorial: Install and use a .NET local tool using the .NET CLI @@ -167,7 +167,7 @@ You typically install a local tool in the root directory of the repository. Afte ## Update a local tool -The installed version of local tool `dotnetsay` is 2.1.3. The latest version is 2.1.4. Use the [dotnet tool update](dotnet-tool-update.md) command to update the tool to the latest version. +The installed version of local tool `dotnetsay` is 2.1.3. Use the [dotnet tool update](dotnet-tool-update.md) command to update the tool to the latest version. ```dotnetcli dotnet tool update dotnetsay @@ -176,7 +176,7 @@ dotnet tool update dotnetsay The output indicates the new version number: ```console -Tool 'dotnetsay' was successfully updated from version '2.1.3' to version '2.1.4' +Tool 'dotnetsay' was successfully updated from version '2.1.3' to version '2.1.7' (manifest file /home/name/repository/.config/dotnet-tools.json). ``` @@ -200,4 +200,4 @@ If you get an error message while following the tutorial, see [Troubleshoot .NET ## See also -For more information, see [.NET Core tools](global-tools.md) +For more information, see [.NET tools](global-tools.md) diff --git a/docs/core/tutorials/cli-templates-create-item-template.md b/docs/core/tutorials/cli-templates-create-item-template.md index 50b53f01f02f8..ec74cd4e05ffa 100644 --- a/docs/core/tutorials/cli-templates-create-item-template.md +++ b/docs/core/tutorials/cli-templates-create-item-template.md @@ -1,15 +1,15 @@ --- -title: Create an item template for dotnet new - .NET Core CLI +title: Create an item template for dotnet new - .NET CLI description: Learn how to create an item template for the dotnet new command. Item templates can contain any number of files. author: adegeo -ms.date: 06/25/2019 +ms.date: 12/11/2020 ms.topic: tutorial ms.author: adegeo --- # Tutorial: Create an item template -With .NET Core, you can create and deploy templates that generate projects, files, even resources. This tutorial is part one of a series that teaches you how to create, install, and uninstall, templates for use with the `dotnet new` command. +With .NET, you can create and deploy templates that generate projects, files, even resources. This tutorial is part one of a series that teaches you how to create, install, and uninstall templates for use with the `dotnet new` command. In this part of the series, you'll learn how to: @@ -23,7 +23,7 @@ In this part of the series, you'll learn how to: ## Prerequisites -* [.NET Core 2.2 SDK](https://dotnet.microsoft.com/download) or later versions. +* [.NET 5.0 SDK](https://dotnet.microsoft.com/download) or a later version. * Read the reference article [Custom templates for dotnet new](../tools/custom-templates.md). The reference article explains the basics about templates and how they're put together. Some of this information will be reiterated here. @@ -80,7 +80,7 @@ Now that you have the content of the template created, you need to create the te ## Create the template config -Templates are recognized in .NET Core by a special folder and config file that exist at the root of your template. In this tutorial, your template folder is located at _working\templates\extensions_. +Templates are recognized by a special folder and config file that exist at the root of your template. In this tutorial, your template folder is located at _working\templates\extensions_. When you create a template, all files and folders in the template folder are included as part of the template except for the special config folder. This config folder is named _.template.config_. @@ -111,7 +111,7 @@ Open the _template.json_ with your favorite text editor and paste in the followi } ``` -This config file contains all the settings for your template. You can see the basic settings, such as `name` and `shortName`, but there's also a `tags/type` value that is set to `item`. This categorizes your template as an item template. There's no restriction on the type of template you create. The `item` and `project` values are common names that .NET Core recommends so that users can easily filter the type of template they're searching for. +This config file contains all the settings for your template. You can see the basic settings, such as `name` and `shortName`, but there's also a `tags/type` value that is set to `item`. This categorizes your template as an item template. There's no restriction on the type of template you create. The `item` and `project` values are common names that .NET recommends so that users can easily filter the type of template they're searching for. The `classifications` item represents the **tags** column you see when you run `dotnet new` and get a list of templates. Users can also search based on classification tags. Don't confuse the `tags` property in the \*.json file with the `classifications` tags list. They're two different things unfortunately named similarly. The full schema for the *template.json* file is found at the [JSON Schema Store](http://json.schemastore.org/template). For more information about the *template.json* file, see the [dotnet templating wiki](https://github.com/dotnet/templating/wiki). @@ -132,14 +132,12 @@ Options: ... cut to save space ... -Templates Short Name Language Tags -------------------------------------------------------------------------------------------------------------------------------- -Example templates: string extensions stringext [C#] Common/Code -Console Application console [C#], F#, VB Common/Console -Class library classlib [C#], F#, VB Common/Library -WPF Application wpf [C#], VB Common/WPF -Windows Forms (WinForms) Application winforms [C#], VB Common/WinForms -Worker Service worker [C#] Common/Worker/Web +Templates Short Name Language Tags +-------------------------------------------- ------------------- ------------ ---------------------- +Example templates: string extensions stringext [C#] Common/Code +Console Application console [C#], F#, VB Common/Console +Class library classlib [C#], F#, VB Common/Library +WPF Application wpf [C#], VB Common/WPF ``` ## Test the item template @@ -204,11 +202,11 @@ You get the following output. !dlroW olleH ``` -Congratulations! You created and deployed an item template with .NET Core. In preparation for the next part of this tutorial series, you must uninstall the template you created. Make sure to delete all files from the _test_ folder too. This will get you back to a clean state ready for the next major section of this tutorial. +Congratulations! You created and deployed an item template with .NET. In preparation for the next part of this tutorial series, you must uninstall the template you created. Make sure to delete all files from the _test_ folder too. This will get you back to a clean state ready for the next major section of this tutorial. ## Uninstall the template -Because you installed the template by file path, you must uninstall it with the **absolute** file path. You can see a list of templates installed by running the `dotnet new -u` command. Your template should be listed last. Use the path listed to uninstall your template with the `dotnet new -u ` command. +Because you installed the template by file path, you must uninstall it with the **absolute** file path. You can see a list of templates installed by running the `dotnet new -u` command. Your template should be listed last. Use the `Uninstall Command` listed to uninstall your template. ```dotnetcli dotnet new -u @@ -220,31 +218,31 @@ You get output similar to the following. Template Instantiation Commands for .NET Core CLI Currently installed items: - Microsoft.DotNet.Common.ItemTemplates + Microsoft.DotNet.Common.ProjectTemplates.2.2 + Details: + NuGetPackageId: Microsoft.DotNet.Common.ProjectTemplates.2.2 + Version: 1.0.2-beta4 + Author: Microsoft Templates: - dotnet gitignore file (gitignore) - global.json file (globaljson) - NuGet Config (nugetconfig) - Solution File (sln) - Dotnet local tool manifest file (tool-manifest) - Web Config (webconfig) + Class library (classlib) C# + Class library (classlib) F# + Class library (classlib) VB + Console Application (console) C# + Console Application (console) F# + Console Application (console) VB + Uninstall Command: + dotnet new -u Microsoft.DotNet.Common.ProjectTemplates.2.2 ... cut to save space ... - NUnit3.DotNetNew.Template - Templates: - NUnit 3 Test Project (nunit) C# - NUnit 3 Test Item (nunit-test) C# - NUnit 3 Test Project (nunit) F# - NUnit 3 Test Item (nunit-test) F# - NUnit 3 Test Project (nunit) VB - NUnit 3 Test Item (nunit-test) VB - C:\working\templates\extensions +C:\Test\templatetutorial\working\templates\extensions Templates: Example templates: string extensions (stringext) C# + Uninstall Command: + dotnet new -u C:\working\templates\extensions ``` -To uninstall a template, run the following command. +To uninstall the template that you created, run the `Uninstall Command` that is shown in the output. ```dotnetcli dotnet new -u C:\working\templates\extensions diff --git a/docs/core/tutorials/cli-templates-create-project-template.md b/docs/core/tutorials/cli-templates-create-project-template.md index 3bfa3507aa173..589ecd3ccc844 100644 --- a/docs/core/tutorials/cli-templates-create-project-template.md +++ b/docs/core/tutorials/cli-templates-create-project-template.md @@ -2,14 +2,14 @@ title: Create a project template for dotnet new description: Learn how to create a project template for the dotnet new command. author: adegeo -ms.date: 06/25/2019 +ms.date: 12/11/2020 ms.topic: tutorial ms.author: adegeo --- # Tutorial: Create a project template -With .NET Core, you can create and deploy templates that generate projects, files, even resources. This tutorial is part two of a series that teaches you how to create, install, and uninstall, templates for use with the `dotnet new` command. +With .NET, you can create and deploy templates that generate projects, files, even resources. This tutorial is part two of a series that teaches you how to create, install, and uninstall, templates for use with the `dotnet new` command. In this part of the series you'll learn how to: @@ -28,7 +28,7 @@ In this part of the series you'll learn how to: ## Create a project template -Project templates produce ready-to-run projects that make it easy for users to start with a working set of code. .NET Core includes a few project templates such as a console application or a class library. In this example, you'll create a new console project that enables C# 8.0 and produces an `async main` entry point. +Project templates produce ready-to-run projects that make it easy for users to start with a working set of code. .NET includes a few project templates such as a console application or a class library. In this example, you'll create a new console project that enables C# 9.0 and produces an `async main` entry point. In your terminal, navigate to the _working\templates_ folder and create a new subfolder named _consoleasync_. Enter the subfolder and run `dotnet new console` to generate the standard console application. You'll be editing the files produced by this template to create a new template. @@ -54,7 +54,7 @@ namespace consoleasync { static async Task Main(string[] args) { - await Console.Out.WriteAsync("Hello World with C# 8.0!"); + await Console.Out.WriteAsync("Hello World with C# 9.0!"); } } } @@ -62,16 +62,16 @@ namespace consoleasync ## Modify consoleasync.csproj -Let's update the C# language version the project uses to version 8.0. Edit the _consoleasync.csproj_ file and add the `` setting to a `` node. +Let's update the C# language version the project uses to version 9.0. Edit the _consoleasync.csproj_ file and add the `` setting to a `` node. ```xml Exe - netcoreapp2.2 + net5.0 - 8.0 + 9.0 @@ -91,16 +91,16 @@ dotnet run You get the following output. ```console -Hello World with C# 8.0! +Hello World with C# 9.0! ``` -You can delete the _obj_ and _bin_ folders created by using `dotnet run`. Deleting these files ensures your template only includes the files related to your template and not any files that result of a build action. +You can delete the _obj_ and _bin_ folders created by using `dotnet run`. Deleting these files ensures your template only includes the files related to your template and not any files that result from a build action. Now that you have the content of the template created, you need to create the template config at the root folder of the template. ## Create the template config -Templates are recognized in .NET Core by a special folder and config file that exist at the root of your template. In this tutorial, your template folder is located at _working\templates\consoleasync_. +Templates are recognized in .NET by a special folder and config file that exist at the root of your template. In this tutorial, your template folder is located at _working\templates\consoleasync_. When you create a template, all files and folders in the template folder are included as part of the template except for the special config folder. This config folder is named _.template.config_. @@ -120,7 +120,7 @@ Open the _template.json_ with your favorite text editor and paste in the followi { "$schema": "http://json.schemastore.org/template", "author": "Me", - "classifications": [ "Common", "Console", "C#8" ], + "classifications": [ "Common", "Console", "C#9" ], "identity": "ExampleTemplate.AsyncProject", "name": "Example templates: async project", "shortName": "consoleasync", @@ -131,7 +131,7 @@ Open the _template.json_ with your favorite text editor and paste in the followi } ``` -This config file contains all of the settings for your template. You can see the basic settings such as `name` and `shortName` but also there's a `tags/type` value that's set to `project`. This designates your template as a project template. There's no restriction on the type of template you create. The `item` and `project` values are common names that .NET Core recommends so that users can easily filter the type of template they're searching for. +This config file contains all of the settings for your template. You can see the basic settings such as `name` and `shortName` but also there's a `tags/type` value that's set to `project`. This designates your template as a project template. There's no restriction on the type of template you create. The `item` and `project` values are common names that .NET recommends so that users can easily filter the type of template they're searching for. The `classifications` item represents the **tags** column you see when you run `dotnet new` and get a list of templates. Users can also search based on classification tags. Don't confuse the `tags` property in the json file with the `classifications` tags list. They're two different things unfortunately named similarly. The full schema for the *template.json* file is found at the [JSON Schema Store](http://json.schemastore.org/template). For more information about the *template.json* file, see the [dotnet templating wiki](https://github.com/dotnet/templating/wiki). @@ -154,19 +154,17 @@ Options: ... cut to save space ... -Templates Short Name Language Tags -------------------------------------------------------------------------------------------------------------------------------- -Console Application console [C#], F#, VB Common/Console -Example templates: async project consoleasync [C#] Common/Console/C#8 -Class library classlib [C#], F#, VB Common/Library -WPF Application wpf [C#], VB Common/WPF -Windows Forms (WinForms) Application winforms [C#], VB Common/WinForms -Worker Service worker [C#] Common/Worker/Web +Templates Short Name Language Tags +-------------------------------------------- ------------------- ------------ ---------------------- +Console Application console [C#], F#, VB Common/Console +Example templates: async project consoleasync [C#] Common/Console/C#9 +Class library classlib [C#], F#, VB Common/Library +WPF Application wpf [C#], VB Common/WPF ``` ### Test the project template -Now that you have an item template installed, test it. +Now that you have a project template installed, test it. 1. Navigate to the _test_ folder @@ -191,14 +189,14 @@ Now that you have an item template installed, test it. You get the following output. ```console - Hello World with C# 8.0! + Hello World with C# 9.0! ``` -Congratulations! You created and deployed a project template with .NET Core. In preparation for the next part of this tutorial series, you must uninstall the template you created. Make sure to delete all files from the _test_ folder too. This will get you back to a clean state ready for the next major section of this tutorial. +Congratulations! You created and deployed a project template with .NET. In preparation for the next part of this tutorial series, you must uninstall the template you created. Make sure to delete all files from the _test_ folder too. This will get you back to a clean state ready for the next major section of this tutorial. ### Uninstall the template -Because you installed the template by using a file path, you must uninstall it with the **absolute** file path. You can see a list of templates installed by running the `dotnet new -u` command. Your template should be listed last. Use the path listed to uninstall your template with the `dotnet new -u ` command. +Because you installed the template by using a file path, you must uninstall it with the **absolute** file path. You can see a list of templates installed by running the `dotnet new -u` command. Your template should be listed last. Use the `Uninstall Command` listed to uninstall your template. ```dotnetcli dotnet new -u @@ -210,31 +208,31 @@ You get output similar to the following. Template Instantiation Commands for .NET Core CLI Currently installed items: - Microsoft.DotNet.Common.ItemTemplates + Microsoft.DotNet.Common.ProjectTemplates.2.2 + Details: + NuGetPackageId: Microsoft.DotNet.Common.ProjectTemplates.2.2 + Version: 1.0.2-beta4 + Author: Microsoft Templates: - dotnet gitignore file (gitignore) - global.json file (globaljson) - NuGet Config (nugetconfig) - Solution File (sln) - Dotnet local tool manifest file (tool-manifest) - Web Config (webconfig) + Class library (classlib) C# + Class library (classlib) F# + Class library (classlib) VB + Console Application (console) C# + Console Application (console) F# + Console Application (console) VB + Uninstall Command: + dotnet new -u Microsoft.DotNet.Common.ProjectTemplates.2.2 ... cut to save space ... - NUnit3.DotNetNew.Template - Templates: - NUnit 3 Test Project (nunit) C# - NUnit 3 Test Item (nunit-test) C# - NUnit 3 Test Project (nunit) F# - NUnit 3 Test Item (nunit-test) F# - NUnit 3 Test Project (nunit) VB - NUnit 3 Test Item (nunit-test) VB - C:\working\templates\consoleasync + C:\Test\templatetutorial\working\templates\consoleasync Templates: Example templates: async project (consoleasync) C# + Uninstall Command: + dotnet new -u C:\working\templates\consoleasync ``` -To uninstall a template, run the following command. +To uninstall the template that you created, run the `Uninstall Command` that is shown in the output. ```dotnetcli dotnet new -u C:\working\templates\consoleasync diff --git a/docs/core/tutorials/cli-templates-create-template-pack.md b/docs/core/tutorials/cli-templates-create-template-pack.md index d947326617838..19a4136f96fcf 100644 --- a/docs/core/tutorials/cli-templates-create-template-pack.md +++ b/docs/core/tutorials/cli-templates-create-template-pack.md @@ -2,14 +2,14 @@ title: Create a template pack for dotnet new description: Learn how to create a csproj file that will build a template pack for the dotnet new command. author: adegeo -ms.date: 12/10/2019 +ms.date: 12/11/2020 ms.topic: tutorial ms.author: adegeo --- # Tutorial: Create a template pack -With .NET Core, you can create and deploy templates that generate projects, files, even resources. This tutorial is part three of a series that teaches you how to create, install, and uninstall templates for use with the `dotnet new` command. +With .NET, you can create and deploy templates that generate projects, files, even resources. This tutorial is part three of a series that teaches you how to create, install, and uninstall templates for use with the `dotnet new` command. In this part of the series you'll learn how to: @@ -79,6 +79,7 @@ Next, open the _templatepack.csproj_ file in your favorite editor and replace th true false content + $(NoWarn);NU5128 @@ -89,11 +90,13 @@ Next, open the _templatepack.csproj_ file in your favorite editor and replace th ``` -The `` settings in the XML above is broken into three groups. The first group deals with properties required for a NuGet package. The three `` value is used to uninstall the template pack with a single name instead of a directory path. It can also be used to install the template pack from a NuGet feed. The remaining settings such as `` and `<PackageTags>` have to do with metadata displayed on the NuGet feed. For more information about NuGet settings, see [NuGet and MSBuild properties](/nuget/reference/msbuild-targets). +The `<PropertyGroup>` settings in the XML above is broken into three groups. The first group deals with properties required for a NuGet package. The three `<Package*>` settings have to do with the NuGet package properties to identify your package on a NuGet feed. Specifically the `<PackageId>` value is used to uninstall the template pack with a single name instead of a directory path. It can also be used to install the template pack from a NuGet feed. The remaining settings such as `<Title>` and `<PackageTags>` have to do with metadata displayed on the NuGet feed. For more information about NuGet settings, see [NuGet and MSBuild properties](/nuget/reference/msbuild-targets). The `<TargetFramework>` setting must be set so that MSBuild will run properly when you run the pack command to compile and pack the project. -The last three settings have to do with configuring the project correctly to include the templates in the appropriate folder in the NuGet pack when it's created. +The next three settings have to do with configuring the project correctly to include the templates in the appropriate folder in the NuGet pack when it's created. + +The last setting suppresses a warning message that doesn't apply to template pack projects. The `<ItemGroup>` contains two settings. First, the `<Content>` setting includes everything in the _templates_ folder as content. It's also set to exclude any _bin_ folder or _obj_ folder to prevent any compiled code (if you tested and compiled your templates) from being included. Second, the `<Compile>` setting excludes all code files from compiling no matter where they're located. This setting prevents the project being used to create a template pack from trying to compile the code in the _templates_ folder hierarchy. @@ -112,7 +115,7 @@ dotnet pack ``` ```console -Microsoft (R) Build Engine version 16.2.0-preview-19278-01+d635043bd for .NET Core +Microsoft (R) Build Engine version 16.8.0+126527ff1 for .NET Copyright (C) Microsoft Corporation. All rights reserved. Restore completed in 123.86 ms for C:\working\templatepack.csproj. @@ -133,12 +136,12 @@ Options: ... cut to save space ... -Templates Short Name Language Tags -------------------------------------------------------------------------------------------------------------------------------- -Example templates: string extensions stringext [C#] Common/Code -Console Application console [C#], F#, VB Common/Console -Example templates: async project consoleasync [C#] Common/Console/C#8 -Class library classlib [C#], F#, VB Common/Library +Templates Short Name Language Tags +-------------------------------------------- ------------------- ------------ ---------------------- +Example templates: string extensions stringext [C#] Common/Code +Console Application console [C#], F#, VB Common/Console +Example templates: async project consoleasync [C#] Common/Console/C#9 +Class library classlib [C#], F#, VB Common/Library ``` If you uploaded the NuGet package to a NuGet feed, you can use the `dotnet new -i PACKAGEID` command where `PACKAGEID` is the same as the `<PackageId>` setting from the _.csproj_ file. This package ID is the same as the NuGet package identifier. @@ -155,29 +158,33 @@ dotnet new -u Template Instantiation Commands for .NET Core CLI Currently installed items: - Microsoft.DotNet.Common.ItemTemplates + Microsoft.DotNet.Common.ProjectTemplates.2.2 + Details: + NuGetPackageId: Microsoft.DotNet.Common.ProjectTemplates.2.2 + Version: 1.0.2-beta4 + Author: Microsoft Templates: - dotnet gitignore file (gitignore) - global.json file (globaljson) - NuGet Config (nugetconfig) - Solution File (sln) - Dotnet local tool manifest file (tool-manifest) - Web Config (webconfig) + Class library (classlib) C# + Class library (classlib) F# + Class library (classlib) VB + Console Application (console) C# + Console Application (console) F# + Console Application (console) VB + Uninstall Command: + dotnet new -u Microsoft.DotNet.Common.ProjectTemplates.2.2 ... cut to save space ... - NUnit3.DotNetNew.Template - Templates: - NUnit 3 Test Project (nunit) C# - NUnit 3 Test Item (nunit-test) C# - NUnit 3 Test Project (nunit) F# - NUnit 3 Test Item (nunit-test) F# - NUnit 3 Test Project (nunit) VB - NUnit 3 Test Item (nunit-test) VB AdatumCorporation.Utility.Templates + Details: + NuGetPackageId: AdatumCorporation.Utility.Templates + Version: 1.0.0 + Author: Me Templates: Example templates: async project (consoleasync) C# Example templates: string extensions (stringext) C# + Uninstall Command: + dotnet new -u AdatumCorporation.Utility.Templates ``` Run `dotnet new -u AdatumCorporation.Utility.Templates` to uninstall the template. The `dotnet new` command will output help information that should omit the templates you previously installed.