I don't even remember where we came up with using "m_" ... maybe a holdover from the old FoxPro days with the "m." syntax. <g>

~~Bonnie


>>I wouldn't use more than one together.
>
>Neither would I, but apparently a lot of developers have other ideas...
>
>>I was just offering a suggestion, based on what Microsoft is doing.
>
>It's appreciated.
>
>
>>The most important thing is to be consistent in whatever you choose. It will make reading your code >much easier for other developers.
>
>Yeah, I couldn't agree more (re: being consistent). I actually find it a little disconcerting to not have a definite naming convention worked out yet in .NET. I like the idea of easy to understand visual clues of "what" a variable is. Not just in the sense of what it represents, but its type. I haven't found anything I've been really happy with yet, so I like to hear what other developers have been doing.
>
>>Bonnie suggested using "m_" instead.
>
>We're actually having this same conversation (eg. naming conventions in .NET) over on the WebConnect messageboard. Another person is also using the "m_" prefix. I'll probably meet everyone halfway and prefix it with just an "m".