Using IntPreview, when I try and create a new project, and searching for blank solution as described in https://docs.microsoft.com/en-us/visualstudio/get-started/tutorial-projects-solutions?view=vs-2019#create-a-solution

Version info:

Microsoft Visual Studio Enterprise 2019 Int Preview
Version 16.9.0 Preview 4.0 [30926.220.main]
VisualStudio.16.IntPreview/16.9.0-pre.4.0+30926.220.main
Microsoft .NET Framework
Version 4.8.04084

Installed Version: Enterprise

ADL Tools Service Provider 1.0
This package contains services used by Data Lake tools

ASA Service Provider 1.0

ASP.NET and Web Tools 2019 16.9.613.9149
ASP.NET and Web Tools 2019

ASP.NET Core Razor Language Services 16.1.0.2107005+6740ea0d8d2f973054c9415f7fb771344a1a1ee6
Provides languages services for ASP.NET Core Razor.

ASP.NET Web Frameworks and Tools 2019 16.9.613.9149
For additional information, visit https://www.asp.net/

Azure App Service Tools v3.0.0 16.9.613.9149
Azure App Service Tools v3.0.0

Azure Data Lake Node 1.0
This package contains the Data Lake integration nodes for Server Explorer.

Azure Data Lake Tools for Visual Studio 2.6.1000.0
Microsoft Azure Data Lake Tools for Visual Studio

Azure Functions and Web Jobs Tools 16.9.613.9149
Azure Functions and Web Jobs Tools

Azure Stream Analytics Tools for Visual Studio 2.6.1000.0
Microsoft Azure Stream Analytics Tools for Visual Studio

C# Tools 3.9.0-4.21075.6+f933691023ee2bcaaa1fdbc6573f0c1e3345d605
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

Common Azure Tools 1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

IntelliCode Extension 1.0
IntelliCode Visual Studio Extension Detailed Info

Microsoft Azure HDInsight Azure Node 2.6.1000.0
HDInsight Node under Azure Node

Microsoft Azure Hive Query Language Service 2.6.1000.0
Language service for Hive query

Microsoft Azure Stream Analytics Language Service 2.6.1000.0
Language service for Azure Stream Analytics

Microsoft Azure Stream Analytics Node 1.0
Azure Stream Analytics Node under Azure Node

Microsoft Azure Tools 2.9
Microsoft Azure Tools for Microsoft Visual Studio 2019 - v2.9.40112.3

Microsoft Continuous Delivery Tools for Visual Studio 0.4
Simplifying the configuration of Azure DevOps pipelines from within the Visual Studio IDE.

Microsoft JVM Debugger 1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines

Microsoft Library Manager 2.1.113+g422d40002e.RR
Install client-side libraries easily to any web project

Microsoft MI-Based Debugger 1.0
Provides support for connecting Visual Studio to MI compatible debuggers

Microsoft Visual Studio Tools for Containers 1.1
Develop, run, validate your ASP.NET Core applications in the target environment. F5 your application directly into a container with debugging, or CTRL + F5 to edit & refresh your app without having to rebuild the container.

NuGet Package Manager 5.9.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/

ProjectServicesPackage Extension 1.0
ProjectServicesPackage Visual Studio Extension Detailed Info

Snapshot Debugging Extension 1.0
Snapshot Debugging Visual Studio Extension Detailed Info

SQL Server Data Tools 16.0.62012.31170
Microsoft SQL Server Data Tools

ToolWindowHostedEditor 1.0
Hosting json editor into a tool window

TypeScript Tools 16.0.30121.2001
TypeScript Tools for Microsoft Visual Studio

Visual Basic Tools 3.9.0-4.21075.6+f933691023ee2bcaaa1fdbc6573f0c1e3345d605
Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

Visual F# Tools 16.9.0-beta.21067.2+9904179c94c41d5d7f9008975d523d807b2a19c6
Microsoft Visual F# Tools

Visual Studio Code Debug Adapter Host Package 1.0
Interop layer for hosting Visual Studio Code debug adapters in Visual Studio

Visual Studio Container Tools Extensions 1.0
View, manage, and diagnose containers within Visual Studio.

Visual Studio Tools for Containers 1.0
Visual Studio Tools for Containers

Repro:

1. Install .NET Core 3.0 SDK
2. Start Blend 2019
3. Press the "Create a new project..." button
4. Search for "class library core"

Expected: The C# and VB "Class Library (.NET Core)" templates appear.

Actual: No matching templates are found.

When using the template installer as shown in https://github.com/phenning/templateSamples/
templates are now shown twice in VS16.9preview (or with the .net core templates turned on in VS16.8 preview settings)

I think we need a good way only show one of them, while still maintaining compatibility with versions where this option if off, or with already published VSIX installers.

By default, template engine redirects the output to a hard disk drive location.
Is it possible to redirect the output of a template engine to an azure blob/file storage path?

Thanks

defaultName option not working as expected with .NET CLI Item templates.

Have defined a defaultName with a valid value in the template.json, but it is never used when a name is not provided while invoking the dotnet new command.

The value for the name always defaults to the current folder name.

From VS Feedback 63803:

All file templates should end with an empty line by convention (and this has been the case, regression!). The C# Console App Program.cs file currently does not have that.

Templates should think about how internationalization (i18n) occurs. By building this into the default templates, I think this would help adoption. Take for example the Console template that mentions "Hello World!". It would be good to have a i18n example here as well.

I have reported this issue through Visual Studio feedback but thought this might be something that Roslyn manages in a private repo for visual studio or corresponds with the appropriate visual studio team. Regardless, editorconfig is Rolyn based so here it is.

The item template C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\ItemTemplates\CSharp\General\EditorConfig\Editorconfig.CS.DotNet.vstemplate points to a dll containing wizard EditorconfigTemplateWizard that generates the .editorconfig file by calling the EditorConfigFileGenerator that incorrectly writes the option names dotnet_style_prefer_inferred_tuple_names and dotnet_style_prefer_inferred_anonymous_type_member_names as dotnet_prefer_inferred_tuple_names and dotnet_prefer_inferred_anonymous_type_member_names respectively. ( These strings are defined in the TemplateConstants static constructor )

1. Start VS or Blend
2. Press "Create a new project" button
3. Select "Visual Basic" in the Language combo box at the top of the New Project dialog
4. Enter "wpf core" in the search box

Expected: "WPF App (.NET Core)" VB template is shown.

Actual: No matches found. But if you change Language to "All Languages" you'll see both of the "WPF App (.NET Core)" templates -- C# and VB.

Looks like there's no associated metadata. See the attached screenshot. The C# template has "C#", "Windows", and "Desktop" tags on it. The VB template doesn't have any.

WinForms has the same issue -- VS only though since Blend doesn't support WinForms.

I just watched the community standup and wanted to add my 2 cents on the debate about main vs. no-main console application template.

Onboarding new developers from Python, PHP, JavaScript or completely new background with a no-using, global-sdk-usings, no-namespace, no-main-method is a very valid goal. I am in for change. global-usings will change how C# programs and app models are defined and I like it very much.

However, do not forget what safety a traditional main-method console template brings to programmers with C, C++ or Java background (aka. fresh converts). Or us 20 year veterans of .NET itself. We like the explicit Main, the usings, the namespace because we expect it. We do not like too much SDK magic like global using System; or auto generated namespaces. Especially for the console app model which should be a vanilla app model (not be too flavored like a e.g. SwiftUI like DSL or a i-will-never-open-program.cs-in-wpf-app). And in sheer numbers we create so much more dotnet new console applications than the current batch of newbies.

What about the following proposal

• dotnet new console with a modern single-line, no-using, global-sdk-usings, no-namespace, no-main-method variant
• dotnet new main for our converts from C, C++, Java and .NET veterans. Just what we always had.
• Adding a comment on the CLI to clarify the situation

  $ dotnet new console
  Creating Console Application
  Hint: If you prefer a console application with a traditional Main method, please use dotnet new main.

@KathleenDollard Hope that helps about the feedback you asked the community.

Repro:

1. Install .NET Core 3.0 SDK
2. Start Blend 2019
3. Press the "Create new project..." hyperlink

Expected: "WPF App (.NET Core)" template appears under the Installed\Visual C#\.NET Core node in the template tree.

Actual: There is no .NET Core node under Installed\Visual C#, and the "WPF App (.NET Core)" isn't found anywhere else.

Today after typing dotnet new we print whole list of templates which makes it very unreadable, all help text that we have for dotnet new is offscren because list of templates is so big...
Solution?
Print only 3-10 templates, we could call this "curated list" or "examples list".

Today there are four entry points to generate an EditorConfig:

1. Right click solution > Add new item:
   

2. Top level menu: File > New File:
   

3. Tools > Options > C# > Code Style > Generate EditorConfig:
   

4. IntelliCode right click menu option in solution explorer:
   

All four entry points should lead to the same scaffolding UI.

1. Scaffold dialog first page:
   

2. Scaffold dialog second page:
   

This issue has been moved from a ticket on Developer Community.

I generated a new c# project under Visual Studio 16.2.3 and build it, FxCop being loaded.
The build succeeded but the number of warnings was impressive.
Of course I can suppress the warnnings, but it would be like driving without brakes.
Could a new release of VS generate code that conforms to the rules
List:
CA5368
CA1056
CA1052
CA1707
CA1716
CA1305
CA1303
CA1062
CA1055
CA1054
CA1822
CA2000
CA1806

Original Comments

Jane Wu [MSFT] on 8/21/2019, 04:17 AM:

Thank you for taking the time to provide your suggestion. We will do some preliminary checks to make sure we can proceed further. We’ll provide an update once the issue has been triaged by the product team.

angular, react and reactredux are included in dotnet template but why dotnet new does not include Vue SPA template?

Resolved by pull request

Version Used:
Version 16.3.0 Preview 3.0 [29221.207.master]

Steps to Reproduce:

Expected Behavior:

Actual Behavior:

16.2:

This issue has been moved from a ticket on Developer Community.

Original Comments

Jane Wu [MSFT] on 3/28/2019, 01:09 AM:

Thank you for taking the time to provide your suggestion. We will do some preliminary checks to make sure we can proceed further. We'll provide an update once the issue has been triaged by the product team.

For example add the text

// Press Ctrl+F5 to run your app
// Go to www.docs.linkhere for a tutorial

Microsoft Visual Studio Enterprise 2022 main (64-bit)
Version 17.0.0 Preview 3.0 [31524.16.main]

The work "Library" should be capitalised. I cannot see that string in this repo.

The shared project templates are currently in the VS repo and use icons and strings from the portal library package. We should consolidate them, and any other relevant templates (AssemblyInfo?) into this repository

Repro

1. Create a new C# Class Library (.NET Standard)
2. Edit the project properties and set the Default Namespace to nothing
3. Add New Item -> Class (Visual C# Items)
4. Observe the invalid code generated

using System;
using System.Collections.Generic;
using System.Text;

namespace 
{
    class Class2
    {
    }
}

Connect all these templates to the correct workloads

I am trying to create a template, where I need to run a postaction powershell script, where the user has to make a choice. However output from write-host is not visible when running it as a postaction for some reason - so I am wondering why that is?

postActions is defined like this to be as simple as possible:
"postActions": [ { "actionId": "3A7C4B45-1F5D-4A30-959A-51B88E82B5D2", "args": { "executable": "powershell", "args": "write-host test" }, "manualInstructions": [ { "text": "Test write-host output in postaction" } ], "continueOnError": false, "description ": "Test write-host output in postaction" }]

However no output can be seen:

For reference, if I run the same command manually it works just fine:

dotnet --info:

.NET Core SDK (reflecting any global.json):
Version: 3.1.100
Commit: cd82f021f4

Runtime Environment:
OS Name: Windows
OS Version: 6.3.9600
OS Platform: Windows
RID: win81-x64
Base Path: C:\Program Files\dotnet\sdk\3.1.100\

Host (useful for support):
Version: 3.1.0
Commit: 65f04fb6db

.NET Core SDKs installed:
2.0.0 [C:\Program Files\dotnet\sdk]
2.0.2 [C:\Program Files\dotnet\sdk]
2.0.3 [C:\Program Files\dotnet\sdk]
2.1.2 [C:\Program Files\dotnet\sdk]
2.1.4 [C:\Program Files\dotnet\sdk]
2.1.101 [C:\Program Files\dotnet\sdk]
2.1.102 [C:\Program Files\dotnet\sdk]
2.1.103 [C:\Program Files\dotnet\sdk]
2.1.104 [C:\Program Files\dotnet\sdk]
2.1.200 [C:\Program Files\dotnet\sdk]
2.1.201 [C:\Program Files\dotnet\sdk]
2.1.202 [C:\Program Files\dotnet\sdk]
2.1.400 [C:\Program Files\dotnet\sdk]
2.1.401 [C:\Program Files\dotnet\sdk]
2.1.402 [C:\Program Files\dotnet\sdk]
2.1.403 [C:\Program Files\dotnet\sdk]
2.1.500 [C:\Program Files\dotnet\sdk]
2.1.502 [C:\Program Files\dotnet\sdk]
2.1.503 [C:\Program Files\dotnet\sdk]
2.1.504 [C:\Program Files\dotnet\sdk]
2.1.505 [C:\Program Files\dotnet\sdk]
2.1.602 [C:\Program Files\dotnet\sdk]
2.1.604 [C:\Program Files\dotnet\sdk]
2.1.700 [C:\Program Files\dotnet\sdk]
2.2.204 [C:\Program Files\dotnet\sdk]
3.0.100 [C:\Program Files\dotnet\sdk]
3.1.100 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.14 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.14 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.14 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Whilst the file ends up getting generated with the right name, the filename shown in the Add Item dialog is showing as editorconfig1 incorrectly. Both csproj and CPS support extension-only filenames so there shouldn't be any reason for this.

In form "Assembly Information" (project properties/application/assembly information/copyright), the input to Copyright have TWO SPACES between "Copyright" and the current year.

This issue has been moved from https://developercommunity.visualstudio.com/content/problem/183772/two-spaces-between-words.html
VSTS ticketId: 553009
These are the original issue comments:
(no comments)
These are the original issue solutions:
(no solutions)

Visual Studio Version:
Microsoft Visual Studio Enterprise 2019 Version 16.7.7
Microsoft Visual Studio Enterprise 2019 main Version 16.9.0 Preview 2.0 [30629.51.main]

Steps to Reproduce:

1. Create a Console App (Net Core)

2. Right-click on the project and add new item

3. Add the item Settings File

4. Build solution

Expected Behavior:
No compilation errors

Actual Behavior:
..\ConsoleApp30\Settings1.Designer.cs(16,76,16,99): error CS1069: The type name 'ApplicationSettingsBase' could not be found in the namespace 'System.Configuration'. This type has been forwarded to assembly 'System.Configuration.ConfigurationManager, Version=4.0.3.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' Consider adding a reference to that assembly.
1>Done building project "ConsoleApp30.csproj" -- FAILED.

User Impact:

I have .NET Core 3.1 installed, when I create a new console application a banner shows up:

An update for template pack Microsoft.DotNet.Common.ProjectTemplates.3.1::3.1.5 is available.
    install command: dotnet new -i Microsoft.DotNet.Common.ProjectTemplates.3.1::5.0.0

Does it make sense this banner shows up for me? Is it important I install this update?
Why aren't updates to the template packs delivered as part of the sdk patch releases?

cc @KathleenDollard

This repo is one of the first seach results when someone search for .NET templates, but it's a bit confusing because these here are the templates for Visual Studio only, not .NET SDK templates ( avaiable in https://github.com/dotnet/templating/ and https://github.com/dotnet/dotnet-template-samples )

Also the repo description is Templates for .NET.

Usually now the templates for .NET (from community and MS) are done like https://docs.microsoft.com/en-us/dotnet/core/tools/custom-templates

For new users can be a bit confusing, because it's a complete different way of do templates.

Maybe this repo be renamed as vs-templates to avoid naming confusion, and the description updated? A note in the readme can be also nice (i can send that as PR if you want).

When you have a .net core template wrapping in a vsix as demonstrated in https://github.com/phenning/templateSamples, you don't get the options the template exposes. With the new v16.9 feature for showing .NET Core templates without the vsix, this becomes very clear.
If you pick the first option here:

You'll be met with this dialog:

However that dialog is skipped if you pick the second option.

You can use this fork of the templateSamples to test it out:
https://github.com/dotMorten/templateSamples/tree/AddTFM

/CC @phenning

If you add a new "Settings" item to a .NET Core project it will cause a build failure if you don't have the System.Configuration.ConfigurationManager package installed.

Error	CS1069	The type name 'ApplicationSettingsBase' could not be found in the namespace 'System.Configuration'. This type has been forwarded to assembly 'System.Configuration.ConfigurationManager, Version=4.0.3.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' Consider adding a reference to that assembly.	Core2	C:\Users\jerem\source\repos\UserSettings\Core2\Settings1.Designer.cs	16	Active

This doesn't happen in a .NET Core WinForms application as Microsoft.WindowsDesktop.App.WindowsForms framwork carries that package.

I'm not sure how things work precisely, but we:

1. Want to keep the template available for Core as it is still a supported scenario
2. Not add the package on .NET Framework apps, only Core, and ideally not when the WindowsForms framework is targeted (as it is redundant in that case)

cc: @ericstj; @maryamariyan

https://github.com/dotnet/templates/tree/master/src/Templates/DotnetCore/Microsoft.NetCore.VB.ProjectTemplates.Desktop

Can we adapt the .NET CLI VS template and check it in here? Please let me know how to proceed.

dotnet/wpf#3866

/cc @dotnet/wpf-developers

@Zheng-Li01 commented on Sun Apr 14 2019

VS: Version 16.1.0 Preview 2 [28811.12.d16.1]
OS: RS3 X64 CHS
.NET Core: 3.0.100-preview4-011198 from Release branch
Affected Languages: CHS, CHT, CSY, DEU, ESN, FRA, ITA, JPN, KOR, PLK, PTB, RUS, TRK

More info:
This issue also can reproduce with all 13 local languages: CHS, CHT, CSY, DEU, ESN, FRA, ITA, JPN, KOR, PLK, PTB, RUS, TRK

Steps to reproduce:

1. Install the .NET Core 3.0 from https://github.com/dotnet/core-sdk.
2. Launch VS and click the ‘Create a new project’ item in the Get started page.
3. Then find the Windows Forms app (.NET Core) template in the Create a new project page.

Actual Result:
The template name ‘Windows Forms app’ is not localized.

Expected Result:
The template name ‘Windows Forms app’ should be localized corresponding to the Framework template name.

@dreddy-work commented on Fri Apr 19 2019

@zsd4yr can you please follow up with @jmarolf on this?

@jmarolf commented on Fri Apr 19 2019

@dreddy-work can you move this issue to dotnet/templates?

Console App
Create an app that can write to and accept input from the command line.

Desktop App
Create an app with a graphical user interface that runs stand-alone on a Windows computer.

Web App
Create an app that can be accessed through any web browser.

Mobile App
Create an app that runs on Android or iOS mobile devices.