Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 4
    This is quite funny considering that the .NET Framework is full of private fields prefixed by m_ Commented Mar 18, 2009 at 19:31
  • I believe irony is the word you're looking for, and yes, the .NET BCL is full of violations of MS's own recommendations. :-P Commented Mar 18, 2009 at 20:55
  • 4
    Actually, the MS guidelines say that internal and private fields are not covered by these guidelines (msdn.microsoft.com/en-us/library/ms229012.aspx ) Commented Jul 26, 2013 at 16:03