IMHO, it’s because converting (both projects and your mind) to VB6 to .NET is hard.
What do you think? Do you have buddies that are still on VB6? What are they doing it about it? Is VB6SP5 "just fine"? Is VB6 a technology that Microsoft should continue to support?
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. I am a failed stand-up comic, a cornrower, and a book author.
Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.