Should enums in C# have their own file? [closed]

Question

I have a class which uses an enumeration, the enum is currently in its own file which seems wasteful.

What is the general opinion on enums being placed within the namespace of a file that they are consumed in? Or should the enum really live in its own cs file?

Edit

I should mention that while the class in question uses these enumerations, so does external callers. In other words, another class can set these enumerations. So they are not used internally to the class, otherwise this question would be a no brainer.

Answer 1

I like to have one public enums file named E containing each seperate enum, then any enum can be accessed with E... and they are in one place to manage.

Answer 2

This is entirely a matter of style. What I tend to do is to have a file called Enums.cs in the solution in which the enum declarations are collected.

But they are typically found through the F12 key anyway.

Answer 3

Another advantage of putting each type (class, struct, enum) in its own file is source control. You can easily get the entire history of the type.