>>>Just like it did for the million of VB6 programmers? :-))
>
>from VB1 to VB6 there was always a clear migration path.
>the jump from VB6 to Visual Studio .NET was the most awkward.
>The migration paths from Visual Studio .NET to VS .NET 2003 and then VS 2005 were all clear.
>
>Therefore, out of roughly 10 version upgrades one was somewhat difficult.
>Likewise, FPD2.6 to FPW2.6 to VFP3 etc etc... all those version upgrades provided a clear migration path... with the 2.6 to 3 being the most difficult.
>
>In order to take on new challenges (back in 1995 it was Visual, OOP, transactional database processing)... you sometimes have to learn a lot between versions.

A big reason for the VB6 to VB.NET gap was because VB.NET wasn't a simple upgrade to VB6. It was a competely new beast that looked somewhat similar.