I started work at the tail-end of the VB6 (legacy systems were maintained with VB6, new work was done in .NET). We lost a lot of good people in the transition.
Unfortunately, many modern developers (including me) avoid VB, in all its incarnations, and there is a fair amount of technical snobbery in the dev world (there always was-even in the VB6 world). The RAD tools currently on the market demo well, but don't seem to lend themselves to more complex use-cases. In the absence of good evidence to the contrary, draggy-droppy RAD is looked down upon, in favor of markup based approaches, and inappropriate complexity is worn as a badge of honor (gross generalization, but I think valid for a substantial chunk of the business development world).
An Agile development process, coupled with a solid RAD platform should yield interesting results.
Unfortunately, many modern developers (including me) avoid VB, in all its incarnations, and there is a fair amount of technical snobbery in the dev world (there always was-even in the VB6 world). The RAD tools currently on the market demo well, but don't seem to lend themselves to more complex use-cases. In the absence of good evidence to the contrary, draggy-droppy RAD is looked down upon, in favor of markup based approaches, and inappropriate complexity is worn as a badge of honor (gross generalization, but I think valid for a substantial chunk of the business development world).
An Agile development process, coupled with a solid RAD platform should yield interesting results.