Home/ Questions/Q 4072244
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T16:51:38+00:00

If I’m dealing with one class and one public struct (not nested), Should I

  • 0

If I’m dealing with one class and one public struct (not nested), Should I create a separate .cs just for the struct? Or leave it un-nested in its .cs file of the class? (This is assuming the struct relates to the class, but isn’t so exclusive to the class that it should be nested and declared private)

Edit: I removed my initial question about two classes because I found C# classes in separate files?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Note that the only person(s) that can accurately answer this question is you, and your team. If your team is happy to find several related types inside a single file, combined due to … whatever… then what I, or whomever other person, says, should be just … irrelevant.

    In any case, I would turn the question upside down:

    • Is there any reason to place two separate types (related by names, functionality, or whatever, but separate nonetheless) in the same file

    and I’ve yet to come up with a good reason.

    There are extensions/addins to Visual Studio where you can type in the name, and quickly navigate to the file, and I can think of three, but there are undoubtedly others:

    The first allows you to quickly navigate to a file by name. If you know the type, but have people putting multiple types into the same type, this will not be helpful, at all.

    The second and third, lets you navigate to a type by name, but you shouldn’t rely on people having those, or knowing how to use them.

    To that end, I would advocate following these rules:

    1. Project names should be identical to the root namespace of that project. I differ from this point myself where in some cases I name my projects “…Core”, and I then remove “Core” from the namespace, but otherwise, leave the project name identical to the namespace
    2. Use folders in the project to build namespace hierarchies
    3. The name of a type should correspond 100% to the name of the file + whatever extension is right for your language. So “YourType” should be “YourType.cs”, “YourType.vb” or “YourType.whatever” depending on language
    • 0