Introduction

Microsoft has always demonstrated a continuing commitment to past and future customers. Sometimes this causes problems. For example, Microsoft had to drag bits of MS-DOS around for years while it patiently waited for customers to update to Windows. Perhaps no greater support has been shown to any other group than developers. After all, Microsoft is a software company that builds tools for software developers, targeting applications intended to run on its own operating systems. With this in mind I would like to offer you some perspective on the transition from VB6 to VB .NET.

One of the riskiest decisions Microsoft had to make regarding .NET was related to Visual Basic 6. Microsoft has a huge following in the VB6 arena ”the largest after Microsoft Office. There are millions of us out there. However, Microsoft realized that innovations in software development methodology and technology mandated an overhaul for Visual Basic 6. When you get into Visual Basic .NET, you might never want to go back to VB6. I know I don't. However, in spite of the desperate need for an overhaul , which has now occurred, Microsoft has not abandoned VB6. We have options, and that's what I would like to talk about.