>>As someone who's in many threads about how VB.NET didn't carry enough baggage from VB6, I was wondering what you mean by VB .NET's syntax baggage compared to C#.
>
>IIRC, some of the changes made in beta2, mostly boolean and array changes, make VB.NET technically not CLR compatible, correct? I would consider that as baggage.

Actually, Microsoft did alot of cleanup of the VB language with .NET. They are caught in the middle. You have the VB6 guys who think that .NET is an upgrade to VB6. It is not. They want to open a VB6 project in .NET, compile it and run it. It won't happen. Then you have the C#/Java group who ridicule VB.NET for not being pure because it tries to maintain backward compatibility.

The baggage that was added to the language was the AndAlso and OrElse expression that avoid the short circuiting that VB6ers are not used to.

http://www.devx.com/dotnet/articles/fb_0628.asp

As far as the definition of True and the array changes (arrays are always 0 based in .NET, 0 or 1 based in VB6 depending on Option Base), Microsoft changed the VB language to remain pure to .NET, not the other way around.

http://www.devx.com/free/hotlinks/2001/ednote011901.asp

-Dave