Microsoft recommends using something like below for your class naming conventions.

VB Code:
  1. public class Customer
  2. {
  3.     string name;
  4.  
  5.     public string Name
  6.     {
  7.       set
  8.       {
  9.         name = value;
  10.       }
  11.          
  12.       get
  13.       {
  14.         return name;
  15.       }
  16.     }
  17. }

Does anyone know why Microsoft wanted to get away from using the m_? It makes it a bit easier to read and know if you see that m_ it is a class variable.

VB Code:
  1. public class Customer
  2. {
  3.     string m_name;
  4.  
  5.     public string Name
  6.     {
  7.       set
  8.       {
  9.         m_name = value;
  10.       }
  11.          
  12.       get
  13.       {
  14.         return m_name;
  15.       }
  16.     }
  17. }

Your thoughts please?