You’d think reading about backward breaking changes from .NET 1.1 to 2.0 would be serious kind of reading, but it’s good to see the VB team has a sense of humour about them. Here’s some of their “bloopers” :
Upgraded apps that use VB Collection through inconsistent implementation of Ilist (very unlikely scenario) may be broken.
I wonder if they meant to imply that upgrading VB6 to VB.NET was a very unlikely scenario
But my favourite one is :
User can add explicit conversions if he wants to convert to a different types than the runtime before doing actual And, Or, Xor operations
Bad luck girls, seems only the guys get to do explicit conversions in VB.NET 2.0 J