>>>>There are lots more, but everyone I've looked at, and heard directly from Microsoft, says, "Don't use Hungarian notation".
>>>>
>>>>
>>>>http://msdn.microsoft.com/en-us/library/ms229002.aspx
>>>>http://idesign.net/idesign/DesktopDefault.aspx (Coding standards link on the right)
>>>>http://www.dotnetspider.com/tutorials/BestPractices.aspx
>>>>http://weblogs.asp.net/lhunt/pages/CSharp-Coding-Standards-document.aspx
>>>>http://10rem.net/articles/net-naming-conventions-and-programming-standards---best-practices
>>>>
>>>>
>>>>>Please provide a link to the grail for .NET naming conventions.
>>>>>
>>>>>From what I'm hearing here, If you have a customer class it would be Customer. If you have a customer form it would be what.. CustomeR?
>>>
>>>But which one is the grail - you know - THE bible of best practices? There must be one, right? If they truly are BEST PRACTICES.
>>
>>Did you find any conflicting advice in those links?
>>Whilst I accept that the guidelines are arbitrary they are in line with the usage in the entire .NET framework.
>>If no-one else is going to have to work with your code then, fine, code how you like.
>>OTOH if that's not the case then follow the guideline and at least make it easier for others to work with it...
>
>I wondering who the god of geeks is that hath delivered the tablets containing the best practices commandments to the mountaintop.

:-}
I guess they originated as coding standards for the original development of the .Net framework. I'd also guess that someone spent a lot of time and effort to determine what works best in terms of readability rather than dreaming it up out of thin air. And, in general, I think they got it right. But, as before, whether you like the guidelines or not, if others have access to your source then common curtesy would suggest that we comply.....