Dotnet CLI showing template (.net core 1.1) which doesn't make any sense now.

[anirugu]

I tried with latest preview release yesterday (preview 5 dotnet7). I curiously search and install few template. I see those template are on Dotnet core 1.1.

These template doesn't make any sense. Either they can be updated or removed (deprecated for better). If there is a way to show it or highlight it at the time of install, it would be great.

I install the first template which got 34K Downloads. if cli can show that this template is this much old, it would be great as well. Currently the way it's work, it can be implemented. If some work is done on cli which help developer to know that template is totally useless now without wasting time to install and create project.

From last paragraph we can say if it's show last updated date, it would be great. or showing the version it's using for project template that would be great as well. This will help the developer to not install the .net core 1.1 template which he/she never going to use. If developer can see this thing from cli, it might help him/her to figure which template would be better.

Describe the bug

A clear and concise description of what the bug is.

To Reproduce

Exceptions (if any)

Further technical details

• Include the output of dotnet --info
• The IDE (VS / VS Code/ VS4Mac) you're running on, and its version

[baronfel]

Moving this to the templating repo, where dotnet new is maintained.

[vlada-shubina]

@baronfel let's discuss possible ways to solve it.
Adding last update date of package should be possible, but I need to double-check if we can get this information.

[vlada-shubina]

We agreed to add last updated date as one of the columns in the list as a viable solution.

Whether it fits default set of columns or not should be investigated. Sorting capability will be desirable: #4885

Identifying the framework required for certain template is not considered atm. This is quite difficult problem due to:

• name of framework parameter is not standardized
• type of framework parameter is not standardized
• the template may contain the projects with hard coded TFMs
• angular example: in this case the dependency on TFM is defined in different way.