Skip to main content

C# 11 – File Scoped Types

One of the new features in C# 11 is File Scoped Types also known as File Local Types. Although it sounds kindof familiar to File Scoped Namespaces introduced in C# 10, it is completely unrelated.

As the name implies File Scoped types restrict the usage of a type to the current file.

The file modifier

To use this feature a new modifier was introduced; file. Applying this modifier to any type definition restrict its usage to the current file.

In the screenshot above you can see that I created a File class in both the FileReader.cs file and FileWriter.cs file without any issues.

If I try to use this File class outside these 2 files, I get an error:

Good to know:

  • The file modifier can be applied to class, interface, record, struct, enum, delegate.
  • It cannot be combined with another modifier like internal or public.

When should I use this feature?

There are a few use cases I can think about where I see this feature useful:

  • Code generation: Code generation is one of the places where naming collisions can easily occur. We typically solve this by using different namespaces With the file keyword it can make code generation a lot easier.
  • Nested classes: One way I use to avoid naming collisions is through private nested classes. Here the file keyword can be a cleaner alternative.

 

What is happening behind the scenes?

To have  a look at what is happening behind the scenes, I opened the compiled code in dotPeek:

As you can see above, the C# compiler renames the types to avoid naming collisions.

Nice!

    Labels:

    Popular posts from this blog

    Podman– Command execution failed with exit code 125

    After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
    Read more

    Azure DevOps/ GitHub emoji

    I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
    Read more

    VS Code Planning mode

    After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
    Read more