Bill Gates announces availability of the VSTO "v3" Community Technology Preview (CTP)

Today at the Office Developer Conference in Redmond, Bill Gates announced the immediate availability of a Community Technology Preview of Visual Studio Tools for Office ‘v3’.  This CTP release works against the Beta 1 Technical Refresh of Microsoft Office 2007.  If you don’t have access to the Beta 1 Technical Refresh of Microsoft Office 2007, don’t despair–there will be another release of the CTP coming later this spring that will work against Office 2007 Beta 2 which will be more widely available.

If you want to read a tutorial that talks about the VSTO ‘v3’ CTP, follow this link.  Kathleen McGrath has also blogged with a video link showing the CTP in action.

The CTP is available for download here and it installs on top of an existing Visual Studio 2005 installation.  Here’s some more info:

This is the March 2006 Community Technology Preview of Microsoft Visual Studio Tools for Office “v3”, planned for the next version of Microsoft Visual Studio (“Orcas”).

Note: This CTP requires you to have the Beta 1 Technical Refresh of Microsoft Office 2007. Only customers currently registered with the Microsoft Office 2007 Beta 1 program (including the Office Developer Conference 2006 attendees) are able to install this CTP. If you are not one of them, there will be another release of this CTP coming later this spring that will be available for installation by the general public.

The primary goal of this CTP is to give Microsoft Office 2007 beta 1 technical refresh developers an early glimpse at some of the key new features and feature directions in the area of Office programmability. The upcoming release of Microsoft Office 2007 introduces a number of new technologies intended to further establish Microsoft Office as a powerful and flexible solution development platform.

The next version of Visual Studio Tools for Office is designed to help developers take better advantage of those new capabilities in Office 2007, as well as to provide additional infrastructure to ensure .NET solutions in Office run more reliably, efficiently and securely.

The highlights of this CTP include:

  • Support for the new Office Open XML file formats in Microsoft Office 2007

  • Support for the new UI ( “ribbon”) extensibility model in Microsoft Office 2007

  • Add-In projects for Microsoft Access 2007, Microsoft Excel 2007, Microsoft SharePoint Designer 2007, Microsoft InfoPath 2007, Microsoft Outlook 2007, Microsoft PowerPoint 2007, Microsoft Project 2007, Microsoft Publisher 2007, Microsoft Visio 2007, and Microsoft Word 2007

  • Support for the new application-level customizable taskpane
Before you install:

As with any pre-release software, you should not install the Visual Studio Tools for Office “v3” CTP on a production machine. Uninstalling this CTP might not bring your computer back to its original state. Hence, it is strongly recommended that you either set up a separate computer for this purpose, or create a backup image of your computer, before installing any of the software referenced here. Alternatively, use a Virtual PC.

Eventually, the next version of Visual Studio Tools for Office will be an independent product, much like the previous versions. Currently however, this CTP is available only as an update to Microsoft Visual Studio 2005. Therefore, in order to install this CTP, you will also need a spare licensed copy of either
Visual Studio 2005 Tools for the Microsoft Office System or Visual Studio 2005 Team System. If you do not have one, then you may download and install Visual Studio 2005 Team Suite 180-Day Trial at no cost from:

You will also need to install
Microsoft WinFX Runtime Components – February Community Technology Preview (CTP).

This Visual Studio Tools for Office “v3” CTP is available in English only.

Comments (7)

  1. Cyril Mathey says:

    Hello Eric,

    I have downloaded the VSTO v3 CTP and I have a couple of questions. I was redirected to your Blog through the VSTO Forum.

    First, I must say that I was rather pleased wth the stability of the CTP. I was able to port a VSTO2005 document-level based customization to an application-level add-in rather quickly.

    My first question is rather simple and concerns Custom Task Panes in a VSTO-based Word Add-In. I want to provide a custom task pane for each opened document. If I wanted to to this in Excel, I would create one task pane instance and dynamically update its contents as the active worksheet changes. As Word uses multiple windows, I guess I need to listen for NewDocument and DocumentOpen events, and create one task pane instance for each document istance. Can you tell me if this the correct approach ?

    My second questions concern the programmability of the custom XML store. I am trying to implement a Word Add-In proof of concept with VSTO that uses a Task Pane (or Ribbon)  to provide the ability to add "Tasks" to an existing document.

    Tasks are described in a custom XML grammar:


     <Task Uuid="…">

       <CreationDate> …</CreationDate>





    When the first task is added to a document, I need to add a new custom XML part to the document. As new tasks are added, I will dynamically udate this XML part by adding new <Task> element. When I add a new task, I also want to insert a boilerplate paragraph that contains contents control mapped to attributes/elements of the newly created task.

    I have started to look at the API and I have found some classes such as CustomXMLParts that I guess I need to use. However, there is no documentation on these classes, and I would  greatly appreciate if you could provide any code sample that you may have concerning this topic. Do not hesitate to tell me if you feel that this CTP is at a too early stage to allow me to implement my POC. I need to have the POC running as soon as possible but I’d rather wait for the next version than loosing time shooting in the dark.

    Thanks a lot in advance for your help.

    — Cyril

  2. Welcome!!!”> google pr. [URL=]pagerank 5[/URL]: pagerank algorithm, Web Site Analysis, SE marketing. Also [url=]online pr16[/url] from google pr .

  3. hello! google pr. pagerank algorithm, Web Site Analysis, SE marketing. From google pr .

  4. Hi, Eric, thank you for publishing the tutorial paper. It works fine to customize the ribbon through an Add In. This way even works in a document (Excel, Word). The trick is to copy the ribbon1.vb and ribbon1.xml to your project (because there is no ribbon-template for document projects available).

    Now: One has to register the assembly for COM interop. Again there is some trouble: you can do this for C# projects for documents, but not for VB projects. It would be a pity if this remains in a final version 🙂

    Thanx for your patience

    Regards Eckehard