C# New Added 2 October 2026

C#: CS0246 The type or namespace name could not be found

The compiler cannot see the type at all. It might be a missing using directive or NuGet package, but just as often the package is there and targets a different framework than the project. Or the type sits in a project that is not referenced. When the IDE is happy and dotnet build is not, a stale obj folder or a mismatched TargetFramework is the usual cause.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix

# Is the package referenced, and for this target framework?
dotnet list package
grep -n TargetFramework *.csproj

# Add the missing package or project reference
dotnet add package Newtonsoft.Json
dotnet add reference ../Shared/Shared.csproj

# Clear stale build output and restore from scratch
dotnet clean
rm -rf bin obj
dotnet restore
dotnet build -v n

How to diagnose C# errors

C# errors divide into compile-time and restore-time problems (NuGet resolution, target framework mismatches) and runtime problems dominated by null references and async misuse. The classic .NET production hazard is the sync-over-async deadlock, calling .Result or .Wait() on a task in a context with a synchronisation context, which manifests as a hang rather than an exception and is therefore much harder to spot.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

Run dotnet restore --verbosity detailed to see which feed each package resolved from. Most restore failures are a private feed with expired credentials, not a missing package.
Enable nullable reference types (<Nullable>enable</Nullable>) and treat the warnings as errors. This converts a whole class of production NullReferenceExceptions into compile failures.
For async hangs, search the codebase for .Result, .Wait() and .GetAwaiter().GetResult(). Replace with await all the way up, or use ConfigureAwait(false) in library code.
For EF Core, run dotnet ef migrations list to see which migrations the database believes are applied before generating a new one.
Capture a dump with dotnet-dump and inspect it with dotnet-gcdump / dotnet-counters when the process misbehaves without throwing.

Tools worth reaching for

dotnet restore -v detailed
dotnet ef migrations list
dotnet-counters
dotnet-dump

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

learn.microsoft.com

Related C# errors

See all 18 C# errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.