<<
First off, you would have to have an accurate grasp on the actual point I made. Bascially, I have contended that a VB developer is not at a material disadvantage to the C# developer.

FWIW, you cannot prove that I am absolutely wrong nor can I prove that I am absolutely right. But since you have lobbed the first shot, the burden of proof is on you to prove I am wrong.

My position is nothing more than my opinion (albeit it is a reasonable and educated one...)

Good luck in your quest...
>>

First off, my apologies for speaking so blunt. You may not wrong but I strongly disagree with you.

Second, you're right in the fact that neither you or I can prove each other wrong or right. Like I told Mike H. - only time will tell and I guarantee you that you will have the VB.Net forum flooded with bug reports and VB.NET Developers crying over the limitations it has.

>>
>
Your statement says it all. A language designed specifically for .NET can exploit the power of the FCL more so than a language adapted to work with the FCL. Unlike other languages, C# has almost no built-in libraries and relies on the FCL, instead.
>

But this necessarily assumes that you will actually need to "exploit the power". I concede that in some cases, you may need to. In the vast majority of cases, at least for the class of applications that most people here development, it is highly unlikely that a developer would need to stray beyond the realm of what VB can do.

I contend that an advantage or feature never used or one that is not likely to be used is a useless feature and is quite literally, useless and perhaps more realistically, not material in the decision making process about whether to choose the language.
>>

No. Not at all. It assumes nothing. It simply means that you can take the C# language to another level where VB.NET would not be able to.

"The vast majority..." I don't know who you've been working with but I've taken applications far beyond the point where VB fell apart. It's bound to happen to VB.NET.

Pinning Object and Using Pointers are features that I bet will be taken advantage of in the very near future. Something VB won't be able to do.

<<
>
Here's a quote from a book from O'reilly : "Many features of C# were designed in response to the strengths and weaknesses of other language..."
>
>Everything points to C# being the next logical step if you're gonna upgrade your skill set.

One quote from a book that is now posited as a general rule. That is quite a leap...< bg >...

I guess YAG is wasting his time at MS.... I guess they should simply shit-can the VB Language....< bg >...

Last I saw, the macro features (which BTW are pretty cool) can only be written in VB... The macro record, which BTW is a great way for learning how the IDE extensibility features work, only produces VB code.

Bottom line Victor, preaching absolutes that one language is NECESSARILY better than one at times may be defensible. However, I would submit that it would only be defensible if the advice were based on sound reasoning. IMO, a quote from a technical book (which 90% are pure crap nowadays) does not have the authoritative weight you accord it today.
>>

I'm not saying that people should abondan VB.NET - however, if someone should ask me "Which Software to use" I would strongly recommend C# and I would state what I've read and what I've experience. It's as simple as that.