FAQ’s: WinFX Add-in model and Visual Studio Tools for Applications (VSTA)
I receive several frequently asked questions on VSTA and the WinFX Add-in model, so I thought I would address them here.
Q: What is Visual Studio Tools for Applications (VSTA)?
A: VSTA is a product and an SDK. At the PDC2005, Eric Rudder, referred to the product as the next generation managed VBA. For more details on the product you can check out this link.
Q: Can you give me the list of VSTA product and SDK features?
A:
· Managed customization support (both app- and doc-level)
· Third process debugging
· WinFX Add-in Model implementation!
o Includes the WinFX Add-in v1.0 components (System.AddIn* NS and dll’s).
· Building and debugging 32bit and 64bit customizations
· Core infrastructure – project system, build/debug support
· Host Project extensibility
· VSTA projects open in VS and vice versa
· Macro recording (via DTE)
· Add-in manager
· Partial Trust Support
· Available via the VSIP program
· SDK – Proxy Generation
· SDK – Generic COM Adapter
· SDK – Generic Managed Adapter
Q: Is it true that I can achieve backward and forward compatibility with my Host application and dynamic .Net components with the WinFX Add-in model?
A: Yes. Check out this link for the ISV VSTA webcast for a demonstration.
Q: Where can I find out more on building managed dynamic .Net components that address versioning, isolation, and unloadability.
A: Here is a link to posts on the WinFX Add-in model. You may also wish to view my webcast at this link.
Q: Is there a webcast on VSTA?
A: Yes, click this link.
Q: Do I need to license VSTA in order to utilize the WinFX Add-in model.
A: No.
Q: The VSTA product seems to be bundled with the VSTA SDK.
A: Correct. The two are currently bundled.
Q: The VSTA product and SDK seem to be related to the VS SDK.
A: Correct. The VS SDK rolls up VSTA.
Q: Does the use of the VSTA SDK, and thus the use of the WinFX Add-in model require me to license the VSTA product?
A: No.
Q: What specifically are the WinFX Add-in model components available through the VSTA SDK?
A: Version 1.0 (v1.0) of System.Addin.dll and System.Addin.Contract.dll.
Q: Does the use of the VSTA SDK, require me to license the VSTA product?
A: No.
Q: How do I get the VSTA product and/or SDK?
A: For more on how to download the VSTA Product and included SDK click here. Note that a passport login is all you need. By clicking on the link “Visual Studio 2005 SDK”, it will start the download process – read as – many bits start downloading via your browser.
Q: Why are the WinFX Add-in components bundled with the VSTA SDK?
A: VSTA was the first implementation of the WinFX Add-in model and the closest shipping vehicle to the Add-in models public availability. As such, the WinFX Add-in model core components shipped as part of the System.AddIn dll’s and namespace prior to their availability in the .Net platform. They will be released as part of the “Orcas” release. The “Orcas” release is the next CLR and VS release.
Q: When does VSTA ship v1.0?
A: The VSTA 2005 product will be released at the same time as Office 2007 (v12). For a preview of Office 2007 click this link.
Q: Are there any major applications integrating the WinFx Add-in model and VSTA product?
A: Yes. As an example, InfoPath 2007 integrated the VSTA Design Time (DT) and Run Time (RT), and built their VS project packages with the VSTA product.
Q: As an ISV, I want to build VS projects for my Add-in developers. What is the recommend method?
A: Use VSTA! VSTA projects are compatible with the VSTA IDE (which is redistributable via the licensing models found here) and the projects you build are also compatible with the VS Pro SKU, which means you can use VS Pro to open VSTA projects.
Q: What is the VSTA blog URL?
A: Click this link.
Updated 06/09/06
Q: Why is the System Add-in collateral referred to as WinFX Add-in?
A: The confusion has been resolved. I will henceforth refer to this solution as System Add-in :-) See this post.
