>Kevin,
>
>Check Message #1208965
>

I'll comment on that message.

Right now one of the things that is most irritating is the instability of VB .NET with design-time expression evaluation. This was introduced in VS 2005 and is near and dear to the hearts of VFP developers because it gives you the ability to run your code at design time in the Immediate Window (similar to the VFP Command Window). This works in conjunction with the Object Test Bench which shows you a visual representation of the objects you instantiate at design time. I wrote an article on the subject that you can read on line:

http://www.utmag.com/ViewPageArticle.aspx?Session=58597A317867364D4174773D206D4B416771704D56625965776D575A774558614A4D773D3D

These aren't features you're likely to use as you're getting started. And by the time you are, Orcas should be released and may fix the things Kevin doesn't like.

My point here is that VB .NET is definitely not "the language of choice" for VFP Developers. Most people claiming that don't work with both languages extensively as I do. It *is* definitely a good choice for some shops, but not the necessarily the best choice--I have worked with several companies who started out with VB .NET then switched to C# because of their frustrations with missing features and lack of "love" from Microsoft.

That's his opinion (although I rank his opinion on this pretty high). Rod Paddock, Beth Massi, Jim Duffy, and others would argue differently. But, they may not spend as much time in both languages as Kevin does.

VB .NET developers often get the "red-headed step child" syndrome that VFP developers have lived with for years. For example, the VS 2005 SDK 4.0 was released a few weeks ago. There are 50 C# samples provided and only one VB .NET. This is a real issue that should be considered when choosing a language.

Beth Massi was just hired by the VB team to fix some of this. As I'm working through my learning process I seem to come across more VB examples than C#, even though I put C# in my search criteria.