I agree with you and am not happy that VB.NET and C#.NET have diverged as they have. I really liked the original concept that they were a "lifestyle choice" that would produce identical CLR code.


>Yes, that happens, but I think there is still a big difference between the VB and C# teams. The VB team seems to be more proactive in looking for things that we can use to be more productive rather than wait for developers to ask for it. David Stevenson posted about one such feature in the past two weeks the he likened to Text Merge. The VB team is implementing it but the C# team doesn't want to do it because they want to keep the language pure and not "pollute" it.
>
>
>>Actually, what often happens (and the C# team is already talking about this) if one language team adds a feature that the other language developers REALLY want, they end up adding it. Often it works the other way around where C# gets a feature that VB developers want but don't have (XML comments, Refactoring, Nullable types) and it eventually gets added to the language or the IDE. Ultimately, there will always be things you want in one language that you will find in the other and vice-versa.
>>
>>Best Regards,