What we've done for fields vs properties (and I don't know if this is standard or not) is for the field to be m_SomeProperty and the property to be SomeProperty.

~~Bonnie

>Hi Paul,
>
>Keep in mind that by using your naming convention it won't be compliant to inherit from these classes for languages that are case insensitive like VB .NET. Microsoft does not encourage using this naming convention and it could limit your classes in the future.
>
>>>Hello,
>>>
>>>I just read through MS naming guidlines for .NET these days and I try to find out why the hell you shouldn't use hungarian notation ?
>>>
>>>I can figure out that it is perhaps a bit confusing if you use cross language and the defined type is not existent in the other language. But I really feel bad about this because it makes my code much more unreadable then it was before. Any ideas why MS want's it this way. Perhaps I can adopt to it easier if I have arguments for this.
>>>
>>
>>Well, I think part of the issue is the fact that, under the hood, everything is an object. In C#, everything is scoped local or is a property of another object. So, what do you use for your prefix? I still haven't decided what type of convention to use yet. About the only thing that I have standardized on is that public properties are Pascal-cased (SomeProperty), while the private member is someProperty.