CS0246 — Type or namespace name could not be found

Environment: C# project compiler; type and namespace resolution.

Identify which dependency is missing

CS0246 concerns a type or namespace, unlike CS0103 which often concerns a local identifier. Possible causes include a missing using directive, an absent project/package reference, a namespace spelling error, a mismatched target framework, or a type that is not publicly accessible.

Reproduce and resolve a missing import

In a C# project without an implicit/global import for System.Collections.Generic, this declaration fails:

using System;
// List<int> values = new(); // CS0246 if Collections.Generic is not imported

Two correct choices are:

using System.Collections.Generic;
List<int> values = new() { 2, 4, 6 };
System.Console.WriteLine(values.Count);

or System.Collections.Generic.List<int> without the import. Expected output: 3. Modern SDK-style templates may provide implicit global usings, so test in a project with that feature disabled or use a distinct missing namespace for a reliable reproduction.

Distinguish imports from references

A using only makes an already-referenced namespace easier to name. It cannot install a NuGet package or add a project dependency. For an external type, inspect the .csproj for PackageReference or ProjectReference, restore dependencies with dotnet restore, and check the package version and target framework. If source code defines the type, verify the namespace declaration and public visibility where projects are separate.

Practical debugging order

1. Read the first CS0246 and note the exact unresolved type.
2. Use a fully qualified type name to test whether it is only an import problem.
3. Search the project for the actual namespace and verify case.
4. Check project references, generated build assets and SDK/target framework; then rebuild.
5. Avoid installing a similarly named random package just because a search result mentions it.

Boundary case

If List<int> builds with no explicit using, inspect ImplicitUsings or global usings before claiming the diagnostic is unreproducible. Compilation context matters.