Introduction

If Visual Studio does not offer .NET Framework 4.8 as a target, the issue is usually missing targeting packs, an unsupported project type, or editing the wrong project property. The runtime being installed on Windows is not enough by itself; Visual Studio also needs the developer targeting components.

Check the Actual Project Style First

There are two common project styles for older .NET applications.

SDK-style projects usually contain:

1<Project Sdk="Microsoft.NET.Sdk">
2  <PropertyGroup>
3    <TargetFramework>net48</TargetFramework>
4  </PropertyGroup>
5</Project>

Older non-SDK projects often use:

<TargetFrameworkVersion>v4.8</TargetFrameworkVersion>

If you edit the wrong element, Visual Studio may ignore your change or show confusing errors. Before doing anything else, open the .csproj file and confirm which style you have.

Install the Developer Pack, Not Just the Runtime

A common source of confusion is that Windows may already have the .NET Framework 4.8 runtime installed, but Visual Studio still cannot target it. That happens because compiling against a framework requires the targeting pack, which is part of the developer pack.

So if the target is missing, verify:

• the .NET Framework 4.8 Developer Pack is installed
• Visual Studio includes the desktop development workload or the relevant individual components
• Visual Studio has been restarted after installation

Without the targeting pack, the IDE may run .NET Framework applications but still refuse to build one that targets 4.8.

Retarget the Project Explicitly

Once the targeting pack is installed, you can usually retarget from the project properties UI or by editing the project file directly.

For an SDK-style project:

1<Project Sdk="Microsoft.NET.Sdk.WindowsDesktop">
2  <PropertyGroup>
3    <OutputType>WinExe</OutputType>
4    <TargetFramework>net48</TargetFramework>
5    <UseWPF>true</UseWPF>
6  </PropertyGroup>
7</Project>

For an older project system:

<PropertyGroup>
  <TargetFrameworkVersion>v4.8</TargetFrameworkVersion>
</PropertyGroup>

After saving the project file, reload the project if Visual Studio prompts you.

Watch for Project-Type Limitations

Some issues are not really about .NET Framework 4.8 itself. They come from the project type.

Examples:

• old setup or installer projects may need separate extensions
• some legacy web project systems behave differently from normal class libraries
• projects converted from very old Visual Studio versions can carry stale imports or toolset assumptions

If the targeting pack is installed but the target still will not appear, inspect the project type before assuming the framework installation failed.

A Practical Diagnostic Sequence

When the IDE refuses to target 4.8, this order keeps the debugging focused:

1. Open the .csproj and identify SDK-style versus legacy style.
2. Confirm the 4.8 developer targeting pack is installed.
3. Confirm the relevant Visual Studio workload or component is installed.
4. Edit the target framework in the project file directly if the UI is misleading.
5. Reload the project and rebuild.

That sequence usually finds the issue faster than repeatedly reinstalling Visual Studio.

Common Pitfalls

The most common mistake is assuming the runtime is the same thing as the targeting pack. It is not. Running an app and compiling an app are separate concerns.

Another mistake is using net48 in a legacy non-SDK project that expects v4.8, or using v4.8 in an SDK-style project that expects net48.

People also forget that .NET Framework 4.8 is different from modern .NET targets such as net8.0. Visual Studio supports both, but they live in different target-framework families and project conventions.

Finally, if the project was upgraded across many Visual Studio releases, stale imports or custom build logic may be the real blocker. In that case, the framework target is only the first visible symptom.

Summary

• Visual Studio needs the .NET Framework 4.8 targeting pack, not just the runtime.
• Confirm whether the project is SDK-style or legacy before editing the target framework.
• Use net48 for SDK-style projects and v4.8 for older project formats.
• If the UI is confusing, edit the .csproj directly and reload the project.
• Project-type quirks can block retargeting even when the framework itself is installed correctly.