Thanks so much for posting your views on it Kevin.


>Tracy,
>
>>Hi Kevin, What do you consider the 'show stoppers' that can be done in C# but NOT in vb.net? Is there a comparison chart anywhere which lists features and limitations in both languages so a comparison can be done?
>
>There aren't a lot of show stoppers right now because VB .NET has caught up to C# features (for the most part). Unfortunately it can takes months or years for this to happen. I'm in a unique position because I write lots of code in both C# and VB .NET and it's been frustrating to have features missing in VB .NET for that period of time.
>
>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

>
>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. 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.
>
>Best Regards,