Just trying to consider everything which may or may not be pertinent to a decision to go with one over the other. In most cases, it is forced upon you due to the business decision made by a company. You can always choose the other if you wish for personal development or just for fun. In my case, I was working (slowly) on learning C# but it looks like it will be VB.net for business apps and C# on my own. Good thing I like research and learning! :o)




>Are you trying to get me back into a c# state of mind? ;-)
>
>>I can't recall them right now, but I recall some posts stating that C# had some features that Vb.net would not. I'll have to search and see if I can locate it now.
>>
>>
>>>
>>>>>>What's to say other teams can't do the same thing using IronPython behind the scenes to handle the dynamic nature of things? With Calvin and Aleksy on the VB team, keep your eyes open for lots of things we do in VFP that make their way into VB. Paul Yuck, the lead PM and Paul Vick, the Calvin of the VB team are pretty bright and understand VFP pretty darn well.
>>>>>>
>>>>>>I was leaning toward C#. A more natural would have been VB.net because I won many books for VB.net. But developers around me kinda convinced me that C# was the way to go. Now you're throwing Calvin in the VB balance. Hmmm I guess I'll get back on the VB track ;-)
>>>>>
>>>>>
>>>>>Try them both out and make up your own mind. Some very good VFP developers have gone one way and some have gone the other. Choose the one that feels comfortable to you.
>>>>
>>>>But Calvin is not an ordinary developper. He helped to make VFP not only make applications with VFP.
>>>>
>>>>But I also respect the feedback of ex-VFP gurus.
>>>
>>>No, Calvin is not an ordinary developer. But he made an unconventional choice way back when, coming out of MIT, and that choice has served him well. All I'm saying is follow your instincts. "This above all, to thine own self be true...."