Resolving Missing Templates in Visual Studio 2017: Installing the .NET Desktop Development Workload

Dec 06, 2025 · Programming · 11 views · 7.8

Keywords: Visual Studio 2017 | .NET Desktop Development | C# Templates

Abstract: This article addresses the issue of missing standard templates (such as C# Console Application and Windows Forms Application templates) after installing Visual Studio 2017. Based on a high-scoring answer from Stack Overflow, it provides a detailed solution by explaining the necessity of installing the ".NET Desktop Development" workload via the Visual Studio Installer. The article contrasts workload installation with individual component selection and offers step-by-step guidance to correctly configure the development environment, avoiding unnecessary component installations and ensuring template availability. It also discusses technical background and best practices, making it suitable for beginners and intermediate users working with C# development in Visual Studio 2017.

Problem Background and Diagnosis

After a fresh installation of Visual Studio 2017 (including RC versions), users often encounter missing standard template lists, particularly crucial for C# development, such as the Console Application (C#) template and Windows Form (C#) template. This is typically due to not selecting necessary workloads during installation. Users may mistakenly believe that these templates can be added manually via the "Individual Components" tab, but the actual solution requires installing a complete workload.

Core Solution: Installing the .NET Desktop Development Workload

According to the high-scoring answer, the key step to resolve this issue is to launch the Visual Studio Installer and install the ".NET Desktop Development" workload. The specific steps are as follows:

  1. Open the Visual Studio Installer (accessible via the Start menu or Control Panel).
  2. In the installer interface, click the "Workloads" tab in the upper-left corner.
  3. In the list on the right, find and check the ".NET Desktop Development" option. This workload includes all components required for C# console application and Windows Forms application templates.
  4. Click the "Install" button, and the installer will automatically download and configure the relevant files. During installation, the estimated size change is displayed at the bottom; users can adjust other workloads as needed, but must ensure ".NET Desktop Development" is selected.

After installation, restart Visual Studio 2017, and the template list should be restored. For example, when creating a new project, users can find templates like Console App (.NET Framework) and Windows Forms App (.NET Framework) under the "Visual C#" category.

Difference Between Workloads and Individual Components

Visual Studio 2017 introduced the concept of workloads to simplify installation and ensure the integrity of the development environment. A workload is a predefined set of components optimized for specific development scenarios (e.g., .NET desktop development, web development). In contrast, the "Individual Components" tab allows users to manually select standalone components, but this can lead to missing dependencies or configuration errors.

In the case of missing templates, users often attempt to install specific templates via the "Individual Components" tab but fail because templates rely on multiple components within a workload working together. For instance, the C# console application template requires components like the .NET Framework SDK, C# compiler, and project system, which are bundled in the ".NET Desktop Development" workload. Therefore, directly installing the workload is a more reliable approach.

Technical Details and Code Example

To deeply understand how templates work, we can illustrate with a simple code example. Assuming a user installs the workload and creates a C# console application, the project file (e.g., .csproj) will contain necessary configurations. Below is a simplified example of project file content, showing how the template defines project structure and dependencies:

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net472</TargetFramework>
  </PropertyGroup>
</Project>

This configuration specifies the output type as an executable and the target framework as .NET Framework 4.7.2, which is part of the ".NET Desktop Development" workload. Without the correct workload installed, Visual Studio cannot resolve these settings, resulting in unavailable templates.

Common Issues and Additional Recommendations

Beyond installing the workload, users should also note the following:

In summary, by installing the ".NET Desktop Development" workload, users can efficiently resolve missing template issues in Visual Studio 2017, ensuring a stable and functional development environment.

Copyright Notice: All rights in this article are reserved by the operators of DevGex. Reasonable sharing and citation are welcome; any reproduction, excerpting, or re-publication without prior permission is prohibited.