>>I know, depends on lots of stuff, but all things being even and a gun to your head, which one would you learn? Ok, things are not even. From what I can tell, VB is a bit easier to learn for Foxpro types, but it looks like C# can pay up to 25% more than VBN. Actually seems like there are more C# jobs too. What do you think?
>
>I think it's a very personal thing. I am going the C# route because I just plain don't feel comfortable in VB.Net. It's the little things. If the damned language knows I forgot to type 'then' at the end of an 'if' line, why doesn't it just add it. Drives me nuts. I also hate being stopped cold just because I didn't finish a line and want to look at something else. But, the bell rings, the round ends, and I have to tell it to leave me alone each and every time. I also like what I think is the more concise nature of C#. VB for me is just a bit too verbose.
>
>Others, I'm sure will disagree with me.
>
>Like I said, it's little things, but I find them annoying enough that I don't want to have to mess with them.
>
>Other than that, I guess it's really six of one, half dozen of the other.

I'm not sure those things would bother me too much. Foxpro pretty much as the same issues, but someone else mentioned how VB was much more verbose that C#. Didn't really think about that much. How is that bad? Doesn't that imply that you get more functionality? If C# can say, "Go do the laundry," but VB can say, "Go do the laundry and make sure the cycle is set to gentle and put some fabric softener in this time," isn't that a good thing? Probably just my total lack of real experience with either language.