Unexpected results when filtering installed templates by type "project"

From @scottaddie on March 5, 2018 21:4

Steps to reproduce

1. Run the following command: dotnet new --type project

Expected behavior

I’d expect to only see project templates listed.

Actual behavior

In addition to project templates, I see the following item templates listed:

1. Solution File
2. Razor Page
3. MVC ViewImports
4. MVC ViewStart

Environment data

dotnet --info output:

.NET Command Line Tools (2.2.0-preview1-007866)

Product Information: Version: 2.2.0-preview1-007866 Commit SHA-1 hash: a99154ed46

Runtime Environment: OS Name: Windows OS Version: 10.0.16299 OS Platform: Windows RID: win10-x64 Base Path: C:\Users\scaddie.dotnet\x64\sdk\2.2.0-preview1-007866\

Microsoft .NET Core Shared Framework Host

Version : 2.1.0-preview1-26103-03 Build : 1d51767c35cb879c2388adf3d76722c6ad658c72

Copied from original issue: dotnet/cli#8727

[seancpeters]

@scottaddie - it’s currently possible to list the templates by a specific language. For example, if you want to see only the F# templates, use: dotnet new -lang F#

In general, if your command line options can’t be resolved to a single template to invoke, a list of the templates that matched the options will be displayed (or if nothing matches the criteria, the entire list will be displayed).

Regarding showing the language for item templates, as long as the template specifies a language, that language will be displayed regardless of the template type. It just happens to be the case that none of the item templates included by default specify a language. You’re absolutely correct that the Razor Page, MVC ViewImports, and MVC ViewStart should include their language. I’ll update the issue I created accordingly.

[scottaddie]

@livarcocc This was fixed via https://github.com/aspnet/templating/pull/343. Feel free to close this issue.