I see these as perceived benefits of C# and perceived weaknesses of VB .NET.

A benefit not taken advantage of provide zero value...




>>You would need to clarify and flesh this out a bit. Could you substantively defend this point? In other words, could you support the thesis that going with C# as opposed to a different CLR langauge that your ROI is "maximized"?
>
>Perhaps you missed my reply to you yesterday when I stated (emphasis is new)
>
>Two major ones, not getting into technical differences like Kevin, would be the available documentation/resources and the fact that C# is an open standard. Meaning that the time I invest into learning C# should be eased by the resources and I could port code to other platforms using the C# standard.
>
>What else does the C# standard mean to me? Since C# is a standard, which is based on other standards (C/C++) when VS.NET 2.0 comes out, I may need to adapt my code for new framework classes, but thats about it. With VB.NET, a proprietary language, it may... and probably will change a little bit. It has in the past, I don't see why it will stop now.
>
>That, and if we view learning C# as a jumpstart to learning other langauges I should be familar with, including but not limited to Java, ECMAScript, C, C++ effectivly supports what I said.
>
>If you did miss it, it was right after I asked what brought you to the conclusion that "people jump on the C# bandwagon cause of the letter C", which you didn't reply to either.