>>And when working with the .NET classes, the code emitted with VB.NET and C# is nearly identical.
>
>Like I said, if you wanna get technical, the claim was true, but I don't even think its relevant.

Sorry, I misunderstood what you were saying. Yes, I would call C# the "purest" of the .NET languages. They really tried to take the best of what Java has to offer.

I find it best to approach .NET with as little baggage as possible. I see VB6 programmers using the FunctionName = ReturnValue instead of using RETURN ReturnValue all the time. With ADO, throw out everything you knew, just learn the new way. Advanced COM+ programmers should have the easiest time since .NET relies heavily on Attribute and Interface programming.

-Dave