Microsoft recommends using something like below for your class naming conventions.
VB Code:
public class Customer { string name; public string Name { set { name = value; } get { return name; } } }
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:
public class Customer { string m_name; public string Name { set { m_name = value; } get { return m_name; } } }
Your thoughts please?




Reply With Quote