D
Diego Diaz
Hello,
I've been taking a look at the new version of MSOffice
(2003) and it looks nice. Nevertheless, I've been
surprised that I had missunderstood about how it would
integrate with .NET. I was expecting to see VSA IDE
(Visual Studio for Applications) in Office 2003 starting
to replace VBA's IDE. However, Office 2003 Developers
Tools are aimed to existing users of Visual Studio.NET
whereas less advanced users/programmers familiar with
Macros have only the old VBA available. I've been
researching about VSA but I haven't quite understood
Microsoft's intend with it.
* Will it be available as an IDE at some point in
MSOffice?
* How can other companies redistribute it as an IDE for
their own .NET-based APIs? At that respect I saw that
Microsoft is pushing the Visual Studio Industry Partner
Program. Does it include VSA? Or is it a separate thing?
I appreciate any clarification on these questions,
Thanks,
Diego Diaz
I've been taking a look at the new version of MSOffice
(2003) and it looks nice. Nevertheless, I've been
surprised that I had missunderstood about how it would
integrate with .NET. I was expecting to see VSA IDE
(Visual Studio for Applications) in Office 2003 starting
to replace VBA's IDE. However, Office 2003 Developers
Tools are aimed to existing users of Visual Studio.NET
whereas less advanced users/programmers familiar with
Macros have only the old VBA available. I've been
researching about VSA but I haven't quite understood
Microsoft's intend with it.
* Will it be available as an IDE at some point in
MSOffice?
* How can other companies redistribute it as an IDE for
their own .NET-based APIs? At that respect I saw that
Microsoft is pushing the Visual Studio Industry Partner
Program. Does it include VSA? Or is it a separate thing?
I appreciate any clarification on these questions,
Thanks,
Diego Diaz