All 10 Modern C# Features (Global Usings, File-Scoped Namespaces, Top-Level Statements) questions
More in Modern C# Features (Global Usings, File-Scoped Namespaces, Top-Level Statements)
What are top-level statements, and how do they simplify a basic C# program's entry point? How do global using directives work, and how do you declare one for an entire project? What does the 'ImplicitUsings' project setting (`<ImplicitUsings>enable</ImplicitUsings>`) do automatically? How do required members (C# 11's 'required' keyword) enforce that certain properties MUST be set during object initialization? How do C# 12's collection expressions (`[1, 2, 3]`) provide a unified, type-agnostic syntax for initializing arrays, lists, and spans? How do C# 12 primary constructors interact with dependency injection in ASP.NET Core minimal APIs and controller classes? How does the 'file' access modifier (C# 11) create a type visible ONLY within its own source file, and what problem does this solve for source generators? How do C# 12's default parameter values on LAMBDA expressions work, and what limitation did they remove compared to earlier C# versions? How do C# 11's raw string literals (`"""..."""`) simplify writing strings containing quotes, escape sequences, or multi-line content like JSON or SQL?
Advertisement
Back to results for “Fundamentals”
C# › Modern C# Features (Global Usings, File-Scoped Namespaces, Top-Level Statements)

What is a file-scoped namespace declaration, and how does it reduce indentation compared to a traditional block-scoped namespace?

Beginner

Answer

A file-scoped namespace (`namespace MyApp.Services;` with a semicolon, no braces) applies to EVERY type declared in the rest of that file, eliminating one level of nested indentation compared to the traditional `namespace MyApp.Services { ... }` block-style syntax — purely a readability/formatting improvement with no behavioral difference.
// Modern: file-scoped namespace, less indentation
namespace MyApp.Services;

public class OrderService { }

// Old: block-scoped namespace, extra indentation level
namespace MyApp.Services {
  public class OrderService { }
}
Real-world example Reducing unnecessary indentation across an entire codebase when every file only ever contains ONE namespace anyway.

Common follow-ups: Can a single file have MULTIPLE file-scoped namespace declarations?

Fundamentals
All 10 Modern C# Features (Global Usings, File-Scoped Namespaces, Top-Level Statements) questions