Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Assuming that the enum or struct is not nested within a particular class i.e. it belongs to the project namespace, should it be defined in:
Enums.cs or Structs.cs where all the enums/structs that belong to the project namespace would be defined
This MSDN article on enum best practices makes no recommendation on where to store enum definitions.
You’ll get different recommendations. Personally, I tend to store enums in the same file as the class they’re related to. I like to keep my file structure the same as my namespace structure, as much as possible, and so if my enums naturally fall into a particular namespace, I’ll store the definition in the corresponding file.
My suggestion is, find a scheme that works for you, and stick with it.