Totally agree with you Rick you any could see my 1st .net Project I had loSqlCmd and loSqlConnection all orver the place now I defile as sqlCmd and sqlConnection when local vars e.g. dim statments and SqlCmd as SqlConnection when properties of an object, also I always use Me. is not necessary but I like to use it since right away as I look into the code I see that is a property from the object and not a parameter or something.

>Michel,
>
>The whole point of hungarian notation was to quickly identify type names and scope. lc and po etc. prefixes are meant to let you see the type and scope of an object. There's much less need for that sort of thing in .NET since you get all of that out of intellisense and strong typing.
>
>I started out with using hungarian, but I quickly realized that it made for more writing and non-standard code. It's simply not necessary.
>
>I will agree that descriptive type names are a good idea - I know the reason articles and books often forego them is for space reasons. It's hard to fit long variable names into the line lengths available for text columns <s>...
>
>All that said I would advise you take a little time to review the guidelines. I think if you start working with .NET more and more you will come to regret the choice to use hungarian just like I did - I'm still going to through some old code and refactoring out that nasty looking code <g>...
>
>+++ Rick ---
>
>
>>>I'm not taking sides, just curious why you think the naming convention in .NET is unorthodox.
>>>
>>>I do have some responses to some of the other things that have been said by others in this thread, but wanted to start with this one.
>>
>>I haven't read an official book on the .NET naming convention topic but after two years in that area, many are saying that most of the samples found on the .NET do contain a good naming convention and I have to disagree. I would say that up to 80% of all the samples I have been faced with during the last two years contains practically zero in regards to that. Or, maybe Google has some kind of condition in it for a search initiated by MF so to return bad examples. :)
>>
>>Here is an example of what I am talking about:
>>
>>

>>Dim dt As New DataTable
>>

>>
>>should have been something like:
>>
>>

>>Dim loDataTableInventory As New DataTable
>>

>>
>>or
>>
>>

>>Dim oDataTableInventory As New DataTable
>>

>>
>>At least, with that, I would know if that is a variable of the method of a property of the object. And, the naming of the entity does contain a good representation of what it is. But, a two-letter word! Outch!