Framework targeting overview

In Visual Studio, you can specify the version of .NET that you want your project to target. Framework targeting helps guarantee that the application uses only functionality that is available in the specified framework version. For .NET Framework apps to run on another computer, the framework version that the application targets must be compatible with the framework version that's installed on the computer.

A Visual Studio solution can contain projects that target different versions of .NET. However, note that you can only build against a single version of .NET either using reference conditionals for a single build or recursively build different binaries for each version. For more information about target frameworks, see Target frameworks.

Tip

You can also target applications for different platforms. For more information, see Multitargeting.

Framework targeting features

Framework targeting includes the following features:

• When you open a project that targets an earlier framework version, Visual Studio can automatically upgrade the project or leave the target as-is.

• When you create a .NET Framework project, you can specify the version of the .NET Framework that you want to target.

• You can target multiple frameworks in a single project.

• You can target a different version of .NET in each of several projects in the same solution.

• You can change the version of .NET that an existing project targets.

  When you change the version of .NET that a project targets, Visual Studio makes any required changes to references and configuration files.

When you work on a project that targets an earlier framework version, Visual Studio dynamically changes the development environment, as follows:

• It filters items in the Add New Item dialog box, the Add New Reference dialog box, and the Add Service Reference dialog box to omit choices that aren't available in the targeted version.

• It filters custom controls in the Toolbox to remove those that aren't available in the targeted version and to show only the most up-to-date controls when multiple controls are available.

• It filters IntelliSense to omit language features that aren't available in the targeted version.

• It filters properties in the Properties window to omit those that aren't available in the targeted version.

• It filters menu options to omit options that aren't available in the targeted version.

• For builds, it uses the version of the compiler and the compiler options that are appropriate for the targeted version.

Note

• Framework targeting does not guarantee that your application will run correctly. You must test your application to make sure it runs against the targeted version.
• You cannot target framework versions below .NET Framework 2.0.

Change the target framework

In an existing Visual Basic, C#, or F# project, you change the target .NET version in the project properties dialog box. For information about how to change the target version for C++ projects, see How to modify the target framework and platform toolset instead.

1. In Solution Explorer, open the right-click context menu for the project that you want to change, and then choose Properties.

2. In the left column of the Properties window, choose the Application tab.

   Note

   After you create a UWP app, you can't change the targeted version of either Windows or .NET.

3. In the Target Framework list, choose the version that you want.

   For a .NET Framework project, the dialog you see might look similar to the following screenshot:

   

   For a .NET project, the dialog might look similar to the following screenshot:

   

4. If a verification dialog box appears, choose the Yes button.

   The project unloads. When it reloads, it targets the .NET version that you just chose.

Note

If your code contains references to a different version of the .NET than the one that you targeted, error messages may appear when you compile or run the code. To resolve these errors, modify the references. See Troubleshoot .NET targeting errors.

Tip

Depending on the target framework, it can be represented in the following ways in the project file:

• For a .NET Core app: <TargetFramework>netcoreapp2.1</TargetFramework>
• For a .NET Standard app: <TargetFramework>netstandard2.0</TargetFramework>
• For a .NET Framework app: <TargetFrameworkVersion>v4.7.2</TargetFrameworkVersion>

Select a target framework version

When you create a .NET Framework project, you can select the target .NET Framework version after you select a project template. The list of available frameworks includes the installed framework versions that are applicable to the selected template type. For non-.NET Framework project templates, for example .NET Core templates, the Framework drop-down list doesn't appear.

If you choose to create a .NET Framework project, you'll see an interface that's similar to the following screenshot:

If you choose to create a .NET project, you'll see user interface (UI) that's similar to the following two screenshots.

The first screen you'll see is the Configure your new project dialog.

The second screen you'll see is the Additional options dialog.

Resolve system and user assembly references

To target a .NET version, you must first install the appropriate assembly references. You can download developer packs for different versions of .NET on the .NET downloads page.

For .NET Framework projects, the Add Reference dialog box disables system assemblies that don't pertain to the target .NET Framework version so that they can't be inadvertently added to a project. (System assemblies are .dll files that are included in a .NET Framework version.) References that belong to a framework version that's higher than the targeted version won't resolve, and controls that depend on such a reference can't be added. If you want to enable such a reference, reset the .NET Framework target of the project to one that includes the reference.

For more information about assembly references, see Resolve assemblies at design time.

Enable LINQ

When you target the .NET Framework 3.5 or later, a reference to System.Core and a project-level import for System.Linq (in Visual Basic only) are added automatically. If you want to use LINQ features, you must also turn Option Infer on (in Visual Basic only). The reference and import are removed automatically if you change the target to an earlier .NET Framework version. For more information, see Work with LINQ.

See also

• Target frameworks
• Multi-targeting (MSBuild)
• How to: Modify the target framework and platform toolset (C++)