Inconsistent accessibility error when exposing a file-scoped type from a public method

Direct answer

Choose internal when a helper type might later need a partial declaration in another file, when a source generator emits the type in one file and a hand-written member consumes it in another, or when you cannot guarantee the type will stay file-private. Choose file only when the type is a true implementation detail, every part and consumer remains in the same source file, and the project uses C# 11 or later. If a public member returns or accepts a file-scoped type, the compiler reports CS0052 because the member’s accessibility domain is wider than the type’s domain.

Why the error appears

The accessibility-domain rule requires that any type exposed in a member signature be at least as accessible as the member itself. A public method exposes its parameter and return types to every assembly that can reference the containing class. A file type is accessible only inside its declaring source file, so callers outside that file cannot name the type. The same mismatch occurs for internal members on public types when the parameter type is file-scoped: the member’s effective domain still crosses the file boundary.

Partial declarations and source generators

file partial types require every part in the same file. Moving one part to another file makes the compiler treat it as a separate, unrelated type. A source generator that emits a file-scoped type into a generated file cannot be consumed by a method in a separate user file unless the generator also emits the consuming member into that same generated file. Otherwise CS0052 appears. Making the generated type internal removes the boundary problem while keeping the type invisible outside the assembly.

When file still makes sense despite cross-file pressure

A team should prefer file only if the helper never appears in a public signature, the consuming code can be co-located in the same file, or cross-file access goes through an internal facade that wraps the file type without returning it in a signature. If the type must cross files in signatures, file is the wrong tool and internal is the minimal fix.

Verification steps

1. Open a C# 11 or later project.
2. In FileA.cs, declare file class Helper {}.
3. In FileB.cs, add public Helper GetHelper() => new();.
4. Build and confirm CS0052 appears.
5. Change the type to internal class Helper or the method to internal Helper GetHelper(), then rebuild; the error should disappear.

To confirm compiler support, run dotnet --info or csc -version and check that the compiler reports version 11.0 or higher. Earlier compilers reject the file keyword before accessibility analysis runs.

Missing diagnostic detail

Do the partial declarations or generated consumers cross assembly boundaries? This determines whether internal is sufficient or whether you need public with InternalsVisibleTo.