On: The worst of the two worlds: Excel meets Outlook

[bsder]

Except that all the little controls and plugins DIDN'T transition to VB.NET--and they're what made VB6 useful to common people.

And the hot code reload in VB.NET is nowhere near as useful as it was in VB6--and that was how common people debugged code.

I can go on and on.

VB.NET was not a useful replacement for VB6. I still know tons of businesses running VB6 code and, when they finally have to migrate, it won't be to VB.NET.

[pjmlp → bsder]

Not enough money to buy little controls from Telerik, ComponentOne, GrapeCity,....?

Interactive .NET sessions have been working for several Visual Studio releases, at least all the way back to 2010.

The only issue is the anti-VB.NET atittude from some VB circles.