I think my number one thing that bothers me is the inconsistency of say typing in MessageBox. then select Show followed by pressing enter and you are off that line while in C# you remain there on Show. MessageBox.Show is simply an example, could be any time one presses enter after selecting a member. Of course if you never plan on using C# or perhaps Javascript this is a moot point.

I am an advocate for coding with Option Strict On yet would guess if a developer coming from VB6 was forced to use Option Strict On that would be a deterrent for them embracing VB.NET. Some place there needs to be a message presented to developers when say using VB.NET for the first time they are encouraged to use Option Strict On.

As VS2015 (and this is not VB.NET spectfic) dropped model first for EF hopefully Microsoft comes up with some good examples for VB.NET developers as in general most are done in C# which should not be an issue for a seasoned VB.NET developer but can be for those just starting out in VB.NET.

I am attending a MVP Summit in November, should be a discussion on this topic as there was a private group of MVP's discussion VB.NET and what it might take to be better for VB.NET developers.