Is VBA going to go away any time soon, like VB6 has? Should I not develop new Office applications with VBA? Or should I be developing all new Office Apps with VSTO?
Update: Recently read this article.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is VBA going to go away any time soon, like VB6 has? Should I not develop new Office applications with VBA? Or should I be developing all new Office Apps with VSTO?
Update: Recently read this article.
Office VSTO offers a great deal of additional functionality over Office VBA, and while I don’t believe Microsoft has signaled that it’s going to terminate VBA (in fact, they’ve said explicitly that it will be around at least until Office 14; Office 2007 = Office 12), I think it’s well worth the effort to move your applications to VSTO to take advantage of the additional flexibility and power.
I actually don’t think that deprecating VBA would be feasible, since a fair amount of Office programming takes place at the macro level by business users and I don’t think that’s going to go away any time soon. Those folks don’t generally have access to a VSTO-capable IDE.