Introduction

System.Windows.Media is part of WPF, not part of general-purpose .NET across every project type. If the namespace cannot be found, the issue is usually not the using line. It is usually that the project is not a WPF project or is not targeting a Windows desktop framework that includes WPF.

That means the fix is normally in project configuration or references, not in the code editor. Once the project is targeting the right stack, the namespace becomes available as expected.

Confirm the Project Is Actually a WPF Project

In an SDK-style project, WPF support is enabled in the .csproj. A minimal working setup looks like this:

1<Project Sdk="Microsoft.NET.Sdk">
2  <PropertyGroup>
3    <OutputType>WinExe</OutputType>
4    <TargetFramework>net8.0-windows</TargetFramework>
5    <UseWPF>true</UseWPF>
6    <Nullable>enable</Nullable>
7  </PropertyGroup>
8</Project>

Two details matter:

• the target framework includes -windows
• 'UseWPF is set to true'

Without those, the project is not wired for WPF namespaces such as System.Windows.Media.

Add the Namespace Only After the Project Supports It

Once the project is configured correctly, normal code compiles as expected:

1using System.Windows;
2using System.Windows.Media;
3
4namespace DemoApp
5{
6    public partial class MainWindow : Window
7    {
8        public MainWindow()
9        {
10            InitializeComponent();
11
12            var brush = new LinearGradientBrush(
13                Colors.SteelBlue,
14                Colors.LightSkyBlue,
15                45
16            );
17
18            Background = brush;
19        }
20    }
21}

If this still fails, the problem is likely reference configuration rather than namespace spelling.

Handle Legacy .NET Framework Projects

For older .NET Framework WPF projects, the expected assemblies include:

• 'PresentationCore'
• 'PresentationFramework'
• 'WindowsBase'

If those references were removed or the project file was edited manually, WPF namespaces can disappear even though the code used to compile.

In that case, inspect the project references in Visual Studio and restore the missing WPF assemblies.

Watch for Cross-Platform and Wrong Project Types

A common source of confusion is trying to use System.Windows.Media in a project type that is not WPF, such as:

• console applications
• ASP.NET projects
• WinForms projects
• cross-platform class libraries

Those project types do not automatically bring in WPF desktop APIs.

If the codebase targets multiple platforms, isolate the WPF-specific code in a Windows-only project or behind platform-specific files instead of trying to share the namespace across every target.

Use a Minimal WPF Check to Isolate the Problem

If you are not sure whether the environment or the solution is broken, a tiny WPF sample is a good sanity check:

1using System.Windows;
2using System.Windows.Controls;
3using System.Windows.Media;
4
5namespace NamespaceCheck;
6
7public partial class App : Application { }
8
9public class MainWindow : Window
10{
11    public MainWindow()
12    {
13        Title = "Media Namespace Test";
14        Width = 400;
15        Height = 200;
16
17        Content = new TextBlock
18        {
19            Text = "System.Windows.Media resolved",
20            Foreground = Brushes.DarkGreen,
21            FontSize = 20,
22            VerticalAlignment = VerticalAlignment.Center,
23            HorizontalAlignment = HorizontalAlignment.Center
24        };
25    }
26}

If that sample builds, the environment is probably fine and the original project has configuration drift.

Common Pitfalls

The biggest mistake is assuming a missing namespace means a missing using directive. With WPF namespaces, the project type is usually the real issue.

Another common problem is targeting plain net8.0 instead of net8.0-windows in a desktop project.

People also mix WPF-specific code into shared libraries that are supposed to build cross-platform. That works only until a non-Windows target tries to compile the same file.

Finally, stale build artifacts can confuse the editor. If the project file is correct but the IDE still complains, clean the solution and rebuild before assuming the configuration is still wrong.

Summary

• 'System.Windows.Media is a WPF namespace, not a general-purpose .NET namespace for every project type.'
• SDK-style projects need a Windows target framework and UseWPF=true.
• Legacy WPF projects need the expected WPF assembly references.
• Keep WPF-specific code out of project types or targets that are not desktop Windows.
• If in doubt, build a minimal WPF sample to separate environment issues from project drift.