title: Naming convention for VB.NET private fields
body: <p>Is there an official convention for naming private fields in VB.NET?  For example, if I have a property called 'Foo', I normally call the private field '_Foo'.  This seems to be frowned upon in the <a href="http://msdn.microsoft.com/en-us/library/ms229012.aspx" rel="noreferrer">Offical Guidelines</a>:</p>
  
  <p>"Do not use a prefix for field names. For example, do not use g_ or s_ to distinguish static versus non-static fields."</p>
  
  <p>In C#, you could call the private field 'foo', the property 'Foo', and refer to the private field as 'this.foo' in the constructor.  As VB.NET is case insensitive you can't do this - any suggestions?</p>