> until VB6-ish started integrating with .NET Minor nitpick :) VB6 never had tooling to integrate with .NET. Rather, .NET could provide an "interop" layer to

> until VB6-ish started integrating with .NET Minor nitpick :) VB6 never had tooling to integrate with .NET. Rather, .NET could provide an "interop" layer to allow you to consume components written in VB6, or just COM in general. You can also create COM visible components written in .NET that could be consumed by VB6 or even scripting languages such as VB script. But the tooling for that was delivered through the .NET SDK/VS. But on your other point, you're right, there are probably a bazillion unknown VB apps out there still chugging along doing their one thing for a specific department or company.