Ron,

>so I don't have to keep hitting the shift key after I've defined a variable. Isn't that what a good IDE should do? But it can't in c#.<

Just a minor nit with that statement ... if you make use of Intellisense, you don't have to worry quite so much about the case of things. Typing "this.m" (no quotes) would bring up a list of your variables that start with an "m" or an "M", so then you can choose MyButton even though you've typed a lower case "m" and the Intellisense will fill it in with the correct case.

~~Bonnie


>>>I still make sure to use the same case, I don't know what anyone would want two variables named MyButton, and myButton and have the compiler not through an error.
>
>Actually, that's my point. No one should want to use two variables named MyButton, and myButton, so vb.net doesn't allow it. Why c# does is beyond me.
>
>>> I think by being more strict, the compiler requires developers to be somewhat more careful, so I would argue case-sensitivity is a pro, as opposed to a con, that same w/ semi-colons.
>
>I think of casing as a mechanical thing, which I'd just as soon the IDE take care of, so I don't have to keep hitting the shift key after I've defined a variable. Isn't that what a good IDE should do? But it can't in c#.
>
>That said, I'll prob go to c# just to have consistency in my code and the 3rd part tools source code, to make it easier to understand them.
>
>An interesting discussion, and it really just comes down to whatever someone feels more comfortable with.
>
>Thanks for the reply.