>
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.
>

I was not looking for an apology. Rather, I was looking for you to be reasonable and to understand that what you asserted had no basis of defensibility.




>
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.
>

But these are features "in the air". It is too generic and sweeping of a statement.

>"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.
>

You need to first determine if you used VB correctly. Somehow, a lot of people have been able to build robust scaleable apps in VB. For sure, there are a lot more of them written in VB than in VFP. Also, assuming a limitation exists in VB, how can you ASSUME VB .NET would have the same problems?

FWIW, I don't think you know how to wield the VB tool in an optimal fashion. As I often say, it is the fiddler, not the fiddle...


>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.
>

Give a concrete practical example of when you would have to do this...


>
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.
<

Sounds like you are softening your stance - from one of technical superiority that could not hold water to one of preference...