VBA code in a VB.Net application (is VSA dead ?)

[Igor Mendizabal]

Hello

We have a VB6 application that integrates an VBA IDE from which the final
user can make modifications.

We want to pass the application to VB.NET, and the first step, before
rethinking the whole application, is to pass the conversion wizard and see
how it goes.

But we want to keep those client VBA modifications working with the least
changes made to them. I've tried integrating VBA in a .NET project but when
I make the VBA IDE visible, I get a COMException ( ErrorCode -2147220119).
The same happens when I converted the VB integration sample of the VBA SDK
to .NET.

I've read that VSA is the substitute to VBA in .NET, but besides I'd have to
tell to all my clients to change all their VBA code to VB.NET code, the last
post I've read about VSA says that the project is dead and to forget about
it.

Anybody was able to integrate VBA (code and IDE) in a .NET app?
Any problems with Interop.MSAPC? Do I have to do it manually?
Is VSA dead?
What are the plans of Microsoft for VBA (or it's substitute)? Which is the
way I should follow?

Thank you very much

Igor Mendizabal
R.P.S.

 

[Howard Kaikow]

Using VB .NET, you can automate an Office app using VBA within the VB .NET
code via the appropriate Office app object.
However, you have to take into account some differences between VB .NET and
VBA.
For example, see MSFT KB article 316383.