W3bbo said:
Bas said:
*snip*

That's what comments are for Smiley

Whilst we're on the subject, I hate having to put Enum member info on their own line in <summary> blocks. I'd prefer it if the C# documentation generator did a similar thing to the C++ doc generator and include // comments made on the same line as the member.

So rather than:

public enum Foo {
    /// <summary>Some member (0xFF)</summary>
    Bar = 0xFF,
    Baz,
}

You can do this:

public enum Foo {
    Bar = 0xFF, // Some member
    Baz,
}

I'd also like it if intellisense showed you the numeric value of an enum member rather than having to put a copy in the <summary> comment.

That bugs me too. Anything that makes you put stuff between the members (like summaries or SuppressMessageAttributes) instantly makes the enum annoying to read.

With regards to numerical values: that always felt dodgy to me, for reasons I can't quite put my finger on. I don't know why, but for some reason it feels wrong to not treat the internal value (and type) as anything other than an internal representation of the enum.

That doesn't stop me from doing it, but it still feels wrong.