>I'm with you on this one Tim!
>
>~~Bonnie
>
>
got to go with what makes sense to me, with reason of course. You almost always make sense. Thanks
Tim

>
>>>Prefacing a control with they type is generally frowned on in the .NET world. Yes, I know it's done alot in sample code. The Framework Design Guidelines say that things should always be spelled out unless they are commonly used/known, for example, Html.
>>
>>Hi Craig,
>>Interesting in the guide that was posted I didn't see anything about this. I do it because it helps me in intellisense like I mentioned. Not sure what the reason or value would be in leaving this off. What if I have a label and a textbox for a customer name. I can easily use lblCustomerName and txtCustomerName with no conflict. What would be the way to do this otherwise without adding Label or Textbox on the end which I fail to find any advantage to?
>>Tim
>>
>>>
>>>
>>>>Hi Mike,
>>>>
>>>>Why do you prefer "SaveOrderButton" instead of "btnSaveOrder" ? All the recommended junk aside, intellisense is a wonderful thing. If I am trying to access a button and I type "this.btn" I will see all my buttons in intellisense. I ususally know it is a button I am looking for but not always if I named it "SaveOrder" or "OrderSave" I am not criticising mind you, I am just curious if there is some reason I am overlooking by having the word "Button" or "Textbox" and if so, why at the end where intellisense has less value.
>>>>
>>>>I never did understand the underscore thing but I know it is popular. It just shows how much I don't like reaching for the underscore button I guess.
>>>>Tim