C# "CS0103: The name X does not exist in the current context" in CI

By Kaveh Alemi·Latchkey

CS0103 means the compiler reached an identifier with no declaration in scope - a typo, a variable that was never declared, an out-of-scope local, or a member used without this./the class name. Unlike CS0246 it is about a name, not a type or namespace reference.

What this error means

Build fails with CS0103 naming the identifier and the line. It is deterministic and tied to the source, so it reproduces on every machine.

dotnet

Service.cs(22,16): error CS0103: The name 'logger' does not exist in the current context

Diagnose it: SDK version and restore first

Most .NET CI failures are an SDK mismatch or a restore that did not happen. global.json pins the SDK, and if the runner does not have that exact version the failure message is about the project rather than the SDK.

Terminal

dotnet --info
cat global.json 2>/dev/null

# restore explicitly so a restore failure is not reported as a build failure
dotnet restore --verbosity normal
dotnet build --no-restore -warnaserror

Common causes

The identifier is misspelled or never declared

A typo or a variable that was removed/renamed leaves the name undeclared in the current scope.

The name is out of scope

A local from another block, or an instance member referenced from a static context, is not visible where it is used.

How to fix it

Declare or correct the identifier

Fix the spelling or declare the missing variable/field.
For a member, qualify it (e.g. this.logger or ClassName.Member).
Rebuild.

.cs

private readonly ILogger _logger;
// ...
_logger.LogInformation("started");

Bring the name into scope

Move the declaration to a scope the usage can see.
Make a static member instance-accessible (or vice versa) as appropriate.
Rebuild.

How to prevent it

Let the IDE/analyzers flag undeclared names before commit.
Keep variable scopes tight and names consistent.
Run a local build before pushing to catch typos.

Frequently asked questions

What causes C# "CS0103: the name X does not exist in the current context" in CI?

There are 2 common causes: the identifier is misspelled or never declared and the name is out of scope. A typo or a variable that was removed/renamed leaves the name undeclared in the current scope.

How do I fix C# "CS0103: the name X does not exist in the current context" in CI?

There are 2 fixes depending on which cause you have: declare or correct the identifier and bring the name into scope. Work through them in order, since the first is the most common.

What does C# "CS0103: the name X does not exist in the current context" in CI actually mean?

Build fails with CS0103 naming the identifier and the line.

How do I stop C# "CS0103: the name X does not exist in the current context" in CI happening again?

Let the IDE/analyzers flag undeclared names before commit. The prevention section lists 3 changes that keep it from recurring.