Introduction

This build error means your machine can run some .NET Framework apps but does not have the developer targeting pack needed to compile against net462. Runtime installation alone is not enough for compilation. The fix is to install the correct reference assemblies and align build tooling across local and CI environments.

Core Sections

Why the Error Appears

MSBuild resolves reference assemblies from targeting packs. If project targets net462 and that pack is missing, compile fails even if .NET Framework runtime exists.

Typical trigger scenarios:

• fresh developer workstation with only modern .NET SDK
• build agent image missing older targeting packs
• Visual Studio upgrade that removed optional components

The project file may look normal:

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

Error is environmental, not usually project syntax.

Install the Correct Developer Pack

On Windows, install .NET Framework 4.6.2 Developer Pack or targeting pack through Visual Studio Installer.

Paths in Visual Studio Installer:

• Individual components
• .NET Framework 4.6.2 targeting pack

After installation, restart shell and rerun build.

msbuild MySolution.sln /t:Restore,Build /v:minimal

Verify Installed Targeting Packs

Check reference assembly directories.

Get-ChildItem "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework" |
  Select-Object Name

You should see folder for v4.6.2 when properly installed.

CI Agent and Build Container Alignment

Many teams fix local machine and forget CI image. Ensure build agents include the same targeting pack.

For self-hosted Windows agents, bake targeting pack into base image. For ephemeral agents, verify startup scripts install required build components.

A simple pre-build check can fail fast:

1$path = "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.6.2"
2if (-not (Test-Path $path)) {
3  throw "Missing .NET Framework 4.6.2 targeting pack"
4}

Multi-Targeting as Migration Strategy

If codebase is moving forward, consider multi-targeting while maintaining legacy compatibility.

<PropertyGroup>
  <TargetFrameworks>net462;net8.0</TargetFrameworks>
</PropertyGroup>

This requires dependency review but reduces long-term lock-in to older framework versions.

NuGet and SDK-Style Project Considerations

SDK-style projects can still target .NET Framework, but toolchain version matters. Keep Visual Studio version and MSBuild consistent with project expectations.

When package restore behaves unexpectedly, clear caches and restore again.

nuget locals all -clear
msbuild MySolution.sln /t:Restore

Build Agent Bootstrap Example

If your CI environment is provisioned by script, include a bootstrap step that checks targeting-pack availability before restore. Fast failure is better than a long build that stops at compile phase with ambiguous logs.

1if (-not (Test-Path \"C:\\Program Files (x86)\\Reference Assemblies\\Microsoft\\Framework\\.NETFramework\\v4.6.2\")) {
2  Write-Error \"Missing net462 reference assemblies\"
3  exit 1
4}

Practical Troubleshooting Order

A reliable sequence:

1. confirm target framework in project file
2. confirm targeting pack installed
3. confirm MSBuild path and version
4. verify CI image parity
5. rerun restore and build

This avoids random edits to project files when root cause is host configuration.

Common Pitfalls

• Installing runtime only and expecting compile references to appear.
• Fixing local machine but ignoring missing packs on CI build agents.
• Changing target framework to silence error without dependency impact review.
• Assuming latest .NET SDK automatically includes all legacy framework packs.
• Debugging package references before checking reference assembly installation.

Summary

• This error is usually caused by missing .NET Framework 4.6.2 targeting pack.
• Runtime installation is not equivalent to compile-time reference assemblies.
• Install and verify targeting pack on both developer and CI machines.
• Keep toolchain versions and build environments aligned.
• Use a deterministic troubleshooting checklist to resolve quickly.