Office Automation
Back to TOCJust VideosCondensed TOC
Automating the Office client applications sometimes is the most effective way to build an application.
- Removing Speaker Notes from a set of PowerPoint Presentations
- Office/SharePoint Building Blocks and Developer Stories
- Overview of Office 2010 Application Development
- Office Application Scenarios
- Understanding the Three Approaches to Office Development using VSTO
- What is the Difference between ‘Word Automation’ and ‘Word Automation Services’?
- Understanding the Architecture of Office 2010 Managed Add-Ins and Customizations
- Understanding the Difference between Custom Task Panes and Action Panes
- Microsoft Word 2010 Developer Building Blocks
- Comparing Excel Automation to Excel Services
- Exploring Tables-of-Contents in Open XML WordprocessingML Documents (Part 3)
Sometimes you want to prepare a set of PowerPoint presentations for distribution outside your company, and you want to remove all speaker notes from the presentations. This is easy enough to do if you only need to scrub a few presentations, but if you have a lot, then manually scrubbing each one will be tedious. (Article)
This post is the first in a series on Microsoft Office 2010 application development. (Article)
You can use a variety of approaches to extend Microsoft Office 2010. There are multiple ways to extend each of the Microsoft Office applications’ user interfaces and programmatically work with the underlying documents, spreadsheets, or presentations. The best way to accomplish your desired objective is not always obvious. (Article)
Many developers identify and document developer scenarios while designing software before writing functional specifications. (Article)
When using Visual Studio Tools for Office (VSTO), there are three basic approaches to Office development: 1) Application-Level Managed Add-In, 2) Document-Level Customization, 3) Office Automation. (Article)
‘Word Automation’ and ‘Word Automation Services’ are two developer building blocks that have similar names, and have overlapping functionality, but are very different pieces of technology. (Article)
The most important technology for building Office applications is that of managed customizations (including application-level managed add-ins, and document-level customizations). Understanding the architecture and capabilities of managed customizations enables you to place the various developer technologies in context. (Article)
To the user, custom task panes and action panes have an identical appearance. Custom task panes and action panes consist of some screen real-estate that co-exists with the open document or spreadsheet within the Office client. This real-estate can be docked to the right, bottom, left, or right of the document or spreadsheet. It can also be a floating window. (Article)
Extending Microsoft Word 2010 is one of the most effective ways to augment content and enable richer collaboration around documents. There are many ways to extend Microsoft Word 2010 and integrate user-friendly and powerful document editing into your application. Extending Word is the most common way to develop for Microsoft Office. (Article)
In a previous post, I compared and contrasted Word Automation to Word Automation Services. There is a similar contrast between Excel Automation and Excel Services, although there is less overlap in functionality when compared to the two approaches for Word. (Article)
In this screen-cast, I show how you can use Word Automation to open and save the document, thereby causing all fields to be updated, including the TOC. (Video)