title: Best practices naming convention for const Enum avoiding circular definition
body: <p>This is sort of a <a href="https://stackoverflow.com/questions/12729147/circular-definition-in-a-constant-enum">duplicate question</a>, but there was no real resolution.</p>
  
  <p>So here we go. Lets say I have:</p>
  
  <pre><code>public enum Color
  {
      Red,
      Blue,
      Green
  }
  
  public class BlueUnicorn
  {
      private const Color Color = Color.Blue;
  }
  </code></pre>
  
  <ol>
  <li><p>"Use a singular name for most Enum types, but use a plural name for Enum types that are bit fields." retreived from <a href="http://msdn.microsoft.com/en-us/library/4x252001%28VS.71%29.aspx" rel="nofollow noreferrer">Microsoft's Enumeration Type Naming Guidelines</a> <strong>Check!</strong></p></li>
  <li><p>"Consider giving a property the same name as its type." retreived from <a href="http://msdn.microsoft.com/en-us/library/ms229012.aspx" rel="nofollow noreferrer">Microsoft's Names of Type Members</a>
  <strong>Check!</strong></p></li>
  <li><p>I should be using a constant instead of readonly, according to Resharper <img src="https://i.stack.imgur.com/P2Vgg.png" alt="enter image description here"><strong>Check!</strong></p></li>
  </ol>
  
  <p>But I get a compiler error. It's odd though, no intellisense on this. <strong>The evaluation of the constant value for 'BlueUnicorn.Color' involves a circular definition.</strong></p>
  
  <p>I feel like I'm in a convention crack here. What should the field be named according to best practices naming convention?</p>