On another forum, I had presented a case that AutoCAD coders (myself included) should not rush to convert their existing VB(A) routines to .NET. That case was based on the premise that if it aint broke, dont fix it, at least not until a significant comfort level with OOP was achieved.
Ideally, the next rewrite would have all routines work within an enterprise wide structure, (Sales, Construction Docs, Accounting, et. al.) a process that may be the most daunting part of the VBA > .NET paradigm shift.
I didnt realize, however, that such a definitive statement had been made with regard to the future of AutoCAD VBA. I guess its time to turn up the burner.