Summit Software

Q:

What is Microsoft VSTA?
back to top

A:

Microsoft Visual Studio Tools for Applications (VSTA) provides ISVs a customization technology allowing them to create more secure, manageable and reliable applications taking advantage of Windows Vista, the 2007 Office System, and additional Microsoft development tools.  VSTA fully supports the .NET framework, and enables development in the Microsoft Visual Basic .NET and Visual C# programming languages. 

At the heart of VSTA is the Managed Add-in Framework (MAF).  MAF is an architectural framework, with basic implementation in WinFx.  MAF can be seen as the .NET equivalent of COM.

Q:

How is VSTA related to Visual Basic for Applications (VBA)?
back to top

A:

VSTA is an entirely separate technology from VBA.

Here is a table describing some of the basic similarities and differences between VBA and VSTA.

* VSTA projects can store projects and assemblies using IStorage, however the projects and assemblies themselves do not require structured storage for persistence.

** VBA can set references to .NET assemblies by creating a COM Interop layer

Q:

Can VSTA and VBA co-exist in the same application?
back to top

A:

Yes.  Microsoft’s does not want its VBA partners to have to “rip and replace” their VBA code to utilize the features of VSTA.  In this case, Microsoft envisions “side-by-side” deployment.  This allows customers to continue to use their existing VBA macro code, while providing VSTA for new customization development.

For an example how to integrate VSTA into an existing, unmanaged VBA-enabled MFC application, click here. 

Q:

What is the difference between VSTA and VSTO?
back to top

A:

VSTO (Visual Studio Tools for Office) was designed to support the building of managed extensions for Office applications.  VSTA was designed to provide the same kind of support for ALL applications, whether managed or unmanaged.  VSTO is built on VSTA technology.

Q:

How does VSTA compare to VS Express?
back to top

A:

VSTA and VS Express are aimed at entirely different spectrums of the developer community.  VSTA is designed for seamless integration into a host application, providing ISVs and IT professionals a robust customization technology.  VS Express Editions are lightweight editions aimed at the hobbyist, novice, and student developer.  As such, the Express editions provide an introduction to a particular aspect of Visual Studio, but do not provide the robust development environment found in VSTA.

Some specific differences:

·         Multiple Language Support:

·         VSTA supports VB.Net and VC#

·         The only VS Express version supporting multiple languages is Visual Web Developer, but this edition is target at web development scenarios, and not rich client development.

·         User Experience

·         While VSTA and VS Express share simplified menu options and defaults, VSTA is more streamlined to remove options/features that are not required for application customization (ie – publishing a solution, creating non-application project types)

·         VSTA provides access to the DTE (Express editions do NOT) and the In-Process Host (IPH) which give the ISV a lot of control over the design-time experience.  In addition to simplifying the integration process, these features enable the ISV to develop powerful end-user features like macro recording and natural entry points.  The ISV has the ability to set the IDE defaults to best suit their application and customer needs.  The IPH also gives the ISV the flexibility to start the IDE from the host application or the Start Menu.

·         Debugging

·         The VSTA IDE supports “external process” debugging so the host application can remain running across debug sessions, and can continue to paint while the add-in is stopped on a breakpoint.

·         Express SKUs only support in-process debugging.

·         Add-Ins

·         The VSTA IDE creates add-ins that work with the VSTA runtime.

·         Using Express SKUs, an ISV will have to approximate VSTA.

·         Versioning and Isolation

·         The VSTA IDE and VSTA runtime provide a powerful customization toolset, ensuring their customer’s investment in add-ins is preserved across multiple versions of the host application; and the ISVs application is protected from malicious or unstable add-ins.

·         Using Express SKUs, an ISV will have to address these issues on their own.

·         64 Bit support

·         The VSTA supports 64 bit applications.

·         Express SKUs provide no 64 bit support.

Q:

What opportunities do VSTA partners have for branding?
back to top

A:

Licensees can brand VSTA in targeted areas.  The help documentation in the SDK provides an overview of what branding is available.  Specifically, see the topics Registering the Host Application and Incorporating the Integrated Development Environment.

Q:

What localized languages will VSTA support?
back to top  

A:

Microsoft will support a number of localized languages.  Here is the current localization plan:

Q:

Will each localized version have its own set of redistributables? 
What is the disk footprint of each set of localized redistributables?
back to top

A:

English ships inside the core MSI and there are two local MSIs for each additional language (one for the IDE and one for the Runtime).  The localized MSI will vary slightly in size depending on the language, but for Japanese, the IDE MSI is 15Mb and the Runtime MSI is 190kb.

Q:

How much does it cost to license VSTA?
back to top

A:

Microsoft offers two licensing models covering the licensing of VSTA, providing licensees the opportunity to select the model that best meets their business needs.  The licensing models are:

Per Seat Licensing:                   $50 per seat

Royalty Model(based on product net receipts):

Low                -                 High                               Royalty Rate

$0                   -          $100,000                                   5%

$100,001        -          $500,000                                   4%