Developing for Microsoft� Office just got exciting again. Microsoft Office XP offers a platform that allows you to provide your end users with a unified desktop environment that integrates their everyday productivity tools with relevant Web-based information delivered just when they need it. This release of Microsoft Office even includes a version, Microsoft Office XP Developer, with a feature set designed especially for the developer.

Whether you're a brand-new developer or a seasoned pro�or somewhere in between�the best place to learn about the new features for developers in Microsoft Office XP is to pick up a copy of Microsoft Office XP Developer's Guide from Microsoft Press�. This essential guide covers everything from the nuts and bolts of Visual Basic� for Applications (VBA) and good coding practices to advanced topics such as developing workflow applications and using digital dashboards. What I really like about this book is that it also includes information on localization and deployment. These are both critical topics in today's increasingly interconnected workplace; unfortunately, they are often overlooked in books for developers, leaving us to learn about best practices through trial and error�often mostly error. To get a feel for the book, check out the table of contents and even read Chapter 12, �Sharing Code with the Code Librarian.�

Microsoft Office XP has more new features than I can cover in detail in a single article. In this article, I'll focus on what I think is the most exciting new feature: Smart Tags. Because the concept is completely new, I will devote a little extra time explaining what Smart Tags are and how you use them in your applications. I'll then walk you through an example that will demonstrate how you can easily build a Smart Tags-based application for your end users by simply modifying my sample code and copying a single file to the users' machines. Along the way, I will give you pointers about where you can find additional information and learn how to build more complex Smart Tags

Office as the Platform for Integrated Applications
Until recently, Microsoft Office with VBA was the development platform of choice for high-profile executive information systems (EIS) and for applications targeted at increasing the productivity of everyday users. Although line of business (LOB) applications often received much of the attention (along with the huge development budgets), the number of end users for these apps was often limited to the staff of a few select departments. If you wanted everyone in your company to use your application, your best bet was to hook it into something everyone used:  Microsoft Office.

What made Office-based applications so valuable (and allowed us as developers to charge big bucks for building them) was their integration. You could develop applications for users whose entire work lives revolved around their favorite productivity application. For example, if you worked for a financial institution and your users were spreadsheet jockeys, you could easily develop an application right inside Microsoft Excel. Not only did your colleagues get an application that looked and acted just like their favorite tool (making it more acceptable to users and at the same time keeping training costs down), but all the data was also in one place.

Then the Internet came along. Nowadays, if you want everyone to use your application, it had better run in a Web browser. Although the standardization on the browser has increased productivity, it creates a split work environment for knowledge workers. The problem is that most users consume Web pages�they don't create with them. For example, you are probably pretty savvy when it comes to the Web�certainly more so then the typical knowledge worker. Do you create your work product with a Web browser? Probably not. Even if you create Web pages for a living, your primary tool is probably a text editor, a word processor, or an e-mail client. Of course you often use a Web browser, but you use it for input into the process, not output.

Typical knowledge workers are no different. They spend the majority of their time reading and creating documents with Microsoft Word or Excel or using Microsoft Outlook� to collaborate with other users. Often these documents or e-mail messages will include a link to an application on the corporate intranet or to an external Web site. The user will click on the link, read some information on the Web site, and then return to the document and continue working on it with the new information.

What is unbelievable to me is that we are so accustomed to this silly, two-step process that we actually consider it an example of good integration between applications. It's like saying that a word processor is integrated with a hardback dictionary. After all, the word processor lets you identify a word that might be misspelled, look it up in the dictionary, and return to the document and correct it if necessary. Maybe I'm just too demanding (or lazy) but if I were a credit manager and I received a document that referenced one of my customers, I would want Microsoft Word to go out and fetch that customer's available credit, payment history, and credit rating and have it waiting for me if I requested it. Sure, this information might be spread out across several internal applications and potentially even on a business partner's extranet, but if I can go find it manually, why can't my software do it for me automatically?

Software is supposed to make life easier. I want it to automate the tedious things I could do manually but would rather not. I want a bot.

Smart Tags: The Office XP Bot
Microsoft Office has (thankfully) gotten rid of Clippy and replaced him with a useful agent: Smart Tags. If you are unfamiliar with the term bot, it is a contraction of �software robot.� A bot is nothing more than a small software program designed to act as a surrogate and autonomously carry out some task on behalf of a user.

If you haven't seen a demo of the new Smart Tag technology yet, think of it as a cross between hyperlinks and IntelliSense�. Adding hyperlinks to documents is nice but has a few drawbacks. First, there is the dichotomy that I've already mentioned between your everyday tools and the browser. Second, you can only associate a single URL with a text string, so only one action is available. Third, hyperlinks are limited to URL-addressable resources such as Web pages, so you have no way to reference data locked in legacy applications that aren't HTTP-aware. As you would expect, Smart Tags solve all these problems.

The Smart Tagfeature has two parts: the underlying architecture and the user interface that exposes that architecture. I'll start with the user interface because that's what you'll see first. Let's say I'm finishing up a letter and I want to include my address under my name. As soon as I press Enter after I type in �Scott Mauvais,� Microsoft Word 2002 recognizes my name as the name of a person and places a purple dotted line under it. When I hover the mouse over the underlined text, the Smart Tag icon (the letter �I� with a circle around it) pops up. I click on the icon to get the list of actions shown in Figure 1.

Figure 1: Smart Tag User Interface

Like the Smart Tag feature, the Smart Tag architecture has two pieces. The Smart Tag Recognizer analyzes and categorizes your text. As you type, Microsoft Office XP fires up a background thread and passes the text to each of the recognizers installed on your system. If one of them recognizes the text as relevant information, Microsoft Office XP places that purple dotted line underneath the text, as you saw earlier. Microsoft ships several sample recognizers with Microsoft Office XP that recognize things such as addresses, stock ticker symbols, and people's names. To see which recognizers are installed on your machine, go to the Tools menu bar, select AutoCorrect Options, and click on the Smart Tags tab. The list should look something like the one in Figure 2.

Figure 2: Smart Tag List

The second part of the architecture is the Smart Tag Action component. As you would expect, this is the module that performs the action you specify on the context menu when you click on the Smart Tag. In the previous example, the Action component inserted my address.

Prior to Microsoft Office XP, inserting someone's address meant firing up Microsoft Outlook, searching for the contact, opening  the contact, navigating to the address information, copying the information and, finally, pasting the information back in the document. I have higher standards for integration. Not only is this a hassle, but it also leaves you open to those embarrassing cut-and-paste errors. With Microsoft Office XP, all this information is readily available to you where you need it and when you need it. Think of Smart Tags as the JIT information delivery system for knowledge management. Unlike Clippy, this Microsoft Office XP bot does useful stuff.

Build Your Own Bot
Inserting contact names and looking up stock symbols is fine, but it's not where the real money is. Smart Tags become really useful (and valuable) when they relate directly to a company's business.

The truly useful implementations of Smart Tags (the ones that will make money for consultants and get in-house developers promoted) will be those that scour everyday Microsoft Word and Excel documents and uncover the hidden nuggets of information that are both specific to the company and relevant to the user. Think about it: every company has many unique terms and associated actions.

Before you start building your own Smart Tags, you need to figure out the key pieces of information that people you work with use everyday. For an agent in an insurance company, this might be a claim ID; for an officer in a loan department, it could be a social security number; for a network administrator, it's probably a machine name or IP address. Once you decide on the key terms, you have to decide how you will recognize them in a document and what actions you will present to users.

Microsoft Office XP exposes two means of recognizing terms. The easiest way is to use the built-in Smart Tag List recognizer and create a Microsoft Office Smart Tag List (MOSTL) file that allows you to create Smart Tags without any code. Keep in mind that the simplicity of a no-code solution comes with some limits on flexibility. These simple Smart Tags can only recognize terms against a static list, and they support only actions that are URL-addressable. This is not as limiting as it sounds. You can configure your Smart Tag List to automatically update itself on a regular basis. For many common types of terms, such as customer and products, updating works fine as long as the lists are not very long. You should stick to a limit of about 5000 items.  You can also pass the Smart Tag text that the user clicked on as a parameter into the Web page you reference. This way you can build  any additional business logic required to provide more information on that end.

If you need more flexibility, such as database lookups or pattern matching, you can create complex Smart Tags by building your own recognizer. You do this by writing code against the Smart Tag API via COM.  All you need to do is implement two interfaces in your DLL: ISmartTagRecognizer and ISmartTagAction.

In the next section, you'll learn how to build simple Smart Tags. To learn how to build complex Smart Tags, see Paul Cornell's �Developing Smart Tag DLLs � article in the May 2001 edition of MSDN�. You'll probably also want to download the Microsoft Office XP Smart Tag SDK 1.1.

Creating Simple Smart Tags
The MOSTL file is the basis for simple Smart Tags. The following listing shows a MOSTL file that defines a Smart Tag to recognize customer IDs from the Northwind database. As you can see, a MOSTL is a simple XML file that follows a schema defined by Microsoft.

Note that the listing here is abridged; to save space, I decided not to list each customer ID.

This is the header section. The table that follows the header describes each element:

<FL:smarttaglist xmlns:FL="urn:schemas-microsoft-com:smarttags:list">
<FL:name>Microsoft Press Sample List</FL:name>
<FL:lcid>1033</FL:lcid>
<FL:description>A list of Northwind Customer IDs.</FL:description>
<FL:moreinfourl>/developer/feature/070501.htm</FL:moreinfourl>
<FL:smarttag type="urn:schemas-microsoft-com:smarttags#mspresssample">
    <FL:caption>Microsoft Press Sample Smart Tag</FL:caption>

Table 1: Header Descriptions

Element Name	Description
Smarttaglist	The root element for a smart tag list definition.
Name	A friendly name for the smart tag recognizer. This is the name the user will see when he or she looks to see which Smart Tags are installed on a given computer. This element is required.
Lcid	A comma-separated list of LocaleIDs, or language identifiers, for which the smart tag list items will be recognized. If the value of this tag is *, 0, or is not specified, the list will work in all locales.
Description	A longer string that describes the smart tag in more detail.
Moreinfourl	A Uniform Resource Locater (URL) where the user can go for more information (supplied by the smart tag developer) about the smart tag recognizer.
Smarttag	The definition of a smart tag type. A smart tag type is defined by a unique namespace, specified as namespaceURI#tagname. This element is required.
Caption	The title caption for the smart tag. This is the text that describes the category when user clicks on the Smart Tag.

The following section defines the terms that will be recognized:

<FL:terms>
    <FL:termlist>ALFKI,ANATR,ANTON,AROUT,BERGS,BLAUS
    </FL:termlist>
</FL:terms>

Table 2: Term Descriptions

Element Name	Description
Terms	A collection of smart tag terms.
Termlist	This is the meat of your Smart Tag. It is a comma-separated list of terms to be recognized. By default, the list is case insensitive. If you want case sensitivity, enclose each term in quotes. This element is required.

The following section defines the actions available to the user when he or she clicks on the Smart Tag:

<FL:actions>
    <FL:action id="MSPress">
        <FL:caption>&amp;MSPress Online </FL:caption>
        <FL:url>/</FL:url>
    </FL:action>
    <FL:action id="MSPressDevFeature">
        <FL:caption>MSPress Developer &amp;Feature Article</FL:caption>
    <FL:url>/developer/Feature/</FL:url>
</FL:action>
    <FL:action id="MSPresSample">
        <FL:caption>&amp;Order History</FL:caption>
        <FL:url>http://www.mauvais.com/Publish/SampleCode/MSPO-SmartTag.asp?{TEXT}</FL:url>
    </FL:action>

Table 3: Action Descriptions

Element Name	Description
Actions	A collection of action elements representing new or revised action identifiers.
Action	An individual action. This element has one attribute called id, which is a required alphanumeric string that uniquely identifies the action that applies to a particular smart tag type.
url	Specifies the URL to activate for an action. If you want to pass the Smart Tag on the query string, append {TEXT} to the URL.
Caption	The action's caption. To include keyboard accelerators, place an ampersand before the character you wish to use as the accelerator. Remember that because this is XML, you will need to escape the ampersand and use &

       
Finally, the closing tags look like this:
</FL:actions>
</FL:smarttag>
</FL:smarttaglist>

There are a few more elements that I did not define. I skipped the ones that deal with automatically updating the MOSTL file by downloading  a new one from a central location. To see how to do this, read Paul Cornell's article �Developing Simple Smart Tags.�

Now that you know how to create an XML file in the  MOSTL format, you can build your own simple Smart Tag. You could start by firing up your favorite text editor, but why bother? It is far easier to download a template I created and modify it for your own uses. Just look for the sections marked TODO: and replace the text with information relevant to you.

Deploying Your Bot
After you finish creating your MOSTL file, the only thing left to do is to deploy your Smart Tag and test it. Deploying simple Smart Tags is easy. Just close down Microsoft Internet Explorer and all Microsoft Office applications and place your XML file  in C:\Program Files\Common Files\Microsoft Shared\Smart Tag\Lists. If you want to automate the process, use the Visual Studio� Installer. For instructions on automating Smart Tag deployment, see Paul Cornell's article �Developing Simple Smart Tags.�

Now fire up Microsoft Word and test your Smart Tag. If everything is working properly, you will see something like Figure 3 when you enter a Northwind Customer ID in a document and click on the associated Smart Tag.

Figure 3:  Smart Tag in Action

Conclusion
This article began by explaining the key components of Smart Tags. I discussed Microsoft Office XP and its ability to provide a complete development platform. From there we looked at some of the limitations users face when trying to integrate Web data into their documents. Then we examined how Smart Tags address the current integration problems and provide a robust environment for giving knowledge workers exactly the information they want exactly when they want it. Finally, we stepped through the process of creating, deploying, and testing a Smart Tag.

Microsoft Press provides in-depth documentation for all issues related to developing for Microsoft Office XP. For a complete list of Microsoft Office XP titles from Microsoft Press, see the Inside Information for Microsoft Office XP page. For titles targeted at developers, see the Microsoft Office XP for Developers and IT Pros page.

The best place to start is with the new Microsoft Office XP Developer's Guide. It allows you to exploit the powerful programmability in Microsoft Office XP with authoritative information straight from the Office XP development team.

Other titles from Microsoft Press you might want to check out include the following:

• Programming Microsoft Office 2000 Web Components will show you how to use Office Web Components (OWC) to build and distribute data analysis and reporting solutions.
  
• Microsoft Office 2000/Visual Basic for Applications Fundamentals is a step-by-step guide for using VBA with each Office 2000 application.
  
• Microsoft Office 2000/Visual Basic Language Reference is the exclusive A-Z documentation of the features, objects, and programming hooks.

Finally, the Inside Out Series from Microsoft Press provides detailed technical information for advanced users. Of particular interest for developers is Microsoft Office XP Inside Out because it will help you better understand what your end users are expecting.

For a complete list of titles related to Microsoft development, see the Microsoft Office for Developers page. For additional resources, you will want to click over to the MSDN Online Office XP Resource page.