Word automation using C#

Word Automation through C# is all about programmatically generating the Word Document using C# code. Almost all of the tasks which we perform on word 2003 can be done programmatically using C# or VB.

1. Development Tools Used

  • Microsoft Visual Studio 2005
  • Microsoft Word 2003
  • Programming Language: C#

2.  Word Automation using C#

Word Automation through C# is all about programmatically generating the Word Document using C# code. Working on Word is considered to be straightforward, but doing the same programmatically gets a little intricate. Word automation almost completely involves working with objects and reference types. Almost all of the tasks which we perform on word 2003 can be done programmatically using C# or VB. Tasks like Inserting Table of Contents, Linking documents, Mail Merge, Inserting Documents, Embedding documents, inserting pictures, watermark... etc can all be done programmatically. 

3. Setting Up Work Environment

Starting off, the first step is to include the Word dll's to the Solution. This can be done by right clicking the Reference Folder in the Solution explorer of the project and select Add Reference.


Figure 1.

Browse Through the available COM objects and Select Microsoft Office 11.0 Object Library & Microsoft Word 11.0 Object Library. This DLL has all the methods which we do to perform the automation.

Note: This dll would be present only if Microsoft Office is installed on the Machine.

Also include "using Microsoft.Office;" in the Namespaces used.


Figure 2.


Figure 3.

4. Objects Used in Automation

All the methods used Word automation is derived either from Word.Application or Word.Document class.

Let's consider that we want to create a document using the Word Application, we might end up doing the following steps,

  1. Open Word Application. (Opening Word Application creates a new document by default, but in Automation, wee need to manually add a document)
  2. Add a New document.
  3. Edit the document.
  4. Save it.

The same steps needs to be done programmatically. The Word.Application and Word.Document are used to Open Word and add a new Document to it.

4.1 Word.Application

This represents in Word Application without any new document loaded in it. This is like the base class which is needed to create a new document. Creating a new instance of Word.Application can be visualized as below.


Figure 4.

4.2 Word.Document

If we need to add a new document file, first we have to create an instance of the Word.Document object and then add it to the Word.Application

  2. Object oMissing = System.Reflection.Missing.Value();  
  4. Object oTrue = true;  
  5. Object oFalse = false;  
  7. Word.Application oWord = new Word.Application();  
  8. Word.Document oWordDoc = new Word.Document();  
  10. oWord.Visible = true;  
  12. oWordDoc = oWord.Documents.Add(ref oMissing, ref oMissing, ref oMissing, ref oMissing);  


This triggers the following operation in the Word Application


Figure 5.

Approaches to Perform Automation

  1. We can either have a base template (.dot) file and open the base template file and work on it.
  2. We can otherwise build a word document from scratch. 

4.3 Standard Input Parameters

Most of the methods have input parameters which are of reference type, and the values are mostly true, false or missing (null). In automation it makes sense as to why most of the input parameters are of reference types; it might be because of the fact that most of the methods a multitude of input parameters (many have more than 10 input parameters) and their value is going to be either true, false or missing in most of the cases. So instead of supplying the same input parameter ten times, we can make all the input parameters point to the location same single variable in them memory. 

4.3.1 Range Object

While we work on Word Application, if we want to type some text in the 11th line, then we manually take the cursor and click it on the required line and then start typing. In order to do the same task, we use the Range variable in C#. The range variable of the Word.Document object represents the location of the cursor on the current document.

There are many possible ways to point to a specific location on a document. I had extensively used the Bookmarks locators as I work on Automation using a base template. In this approach, we insert Bookmarks on the base template and we programmatically locate those Bookmarks, set the range on them and insert text or documents at that specific location. There are also many other possible ways to set the range.

  2. Object oBookMarkName = "My_Inserted_Bookmark_On_Template";  
  3. Word.Range wrdRange = oWordDoc.Bookmarks.get_Item(ref oBookMarkName).Range.Select();  
4.3.2 Selection Object

While working on word, we select a range of text by clicking and dragging the mouse pointer across contents in the document to select it. The contents can be text, formatted text, tables or any other item in the document. We programmatically represent the same by using the Selection Object derived from Word.Selection. In the previous range example, we locate a bookmark and set the range on that specific bookmark and we select it. Now the selection object represents that specific location. It's like placing the cursor on that specific bookmark location on the document. The selection across text can be done by selecting a range of text in between two ranges. Then the selected range can be copied, deleted or formatted.

4.3.3 Selecting Between Bookmarks

  2. Object oBookmarkStart = "BookMark__Start";  
  3. Object oRngoBookMarkStart = oWordDoc.Bookmarks.get_Item(ref oBookmarkDesignInfoStart).Range.Start;  
  5. Object oBookmarkEnd = "BookMark__End";  
  6. Object oRngoBookMarkEnd = oWordDoc.Bookmarks.get_Item(ref oBookmarkDesignInfoEnd).Range.Start;  
  8. Word.Range rngBKMarkSelection = oWordDoc.Range(ref oRngoBookMarkStart, ref oRngoBookMarkEnd);  
  10. rngBKMarkSelection.Select();  
  11. rngBKMarkSelection.Delete(ref oMissing, ref oMissing);  
5. Automation using a Base Template

The base template file method is preferable as it gives us much more flexibility in performing the automation and it comes very handy for performing Mail Merge.

In the base template method, when we call the Documents.Add method of the Application object, we give the path of the .dot file.

  2. Object oTemplatePath = "C:\\Program Files\\MyTemplate.dot";  
  4. oWordDoc = oWord.Documents.Add(ref oTemplatePath, ref oMissing, ref oMissing, ref oMissing);  
Now .dot file is opened and when we save the generated document, we save it as a new file. 

6. Mail Merge

Mail merge is a useful tool in scenarios where we want to randomly generate alike documents where just a few fields change. For instance in a pay slip which has a base template and just the employee name, number and pay details needs to change for each employee. Now we can have a base template which is a word file saved as Document Template file.

In the .dot file, insert a Mail Merge Field manually by placing the cursor in the required position and Insert -> Field, and in Field Names, select "MergeField", now the Mail merged field would be represented by <<FieldName>>. The template can be like

Contact Information

For further information and discussions, please contact:

Name: <<CIFLName>>
Address: <<CIAddress>>
Phone:  <<CIPhW>> (Work)
Fax:      <<CIFax>>
Email    <<CIMail>>

Now for programmatically replacing the Mail Merge fields using the code, the document by default has many fields in it. But the user entered fields comes with a prefix and suffix which can be can be used as an identifier to replace the fields.

  2. Object oMissing = System.Reflection.Missing.Value();  
  4. Object oTrue = true;  
  5. Object oFalse = false;  
  7. Word.Application oWord = new Word.Application();  
  8. Word.Document oWordDoc = new Word.Document();  
  10. oWord.Visible = true;  
  12. Object oTemplatePath = "C:\\Program Files\\MyTemplate.dot";  
  14. oWordDoc = oWord.Documents.Add(ref oTemplatePath, ref oMissing, ref oMissing, ref oMissing);  
  15. foreach (Word.Field myMergeField in oWordDoc.Fields)  
  16. {  
  17.     iTotalFields++;  
  18.     Word.Range rngFieldCode = myMergeField.Code;  
  19.     String fieldText = rngFieldCode.Text;  
  21.     if (fieldText.StartsWith(" MERGEFIELD"))  
  22.     {  
  23.         // THE TEXT COMES IN THE FORMAT OF  
  24.         // MERGEFIELD  MyFieldName  \\* MERGEFORMAT  
  26.         Int32 endMerge = fieldText.IndexOf("\\");  
  27.         Int32 fieldNameLength = fieldText.Length - endMerge;  
  28.         String fieldName = fieldText.Substring(11, endMerge - 11);  
  30.         fieldName = fieldName.Trim();  
  33.         if (fieldName == "MyField")  
  34.         {  
  35.             myMergeField.Select();  
  36.             oWord.Selection.TypeText("This Text Replaces the Field in the Template");  
  37.         }  
  38.     }  
  39. }  
There is one other method for replacing the Merge Fields which is mentioned in msdn, which uses a rather memory hungry approach. In that method a separate document is opened and it is inserted with a table which has first row as the Mail Merge Field Name and the second row as the replacement value, then the value from the table is matched with that of the original document and replacement occurs and the second document is purged.

7. Embedding a Document

Embedding a document is done through the application by

Insert-> Object-> Create from file-> Select the File-> Display as Icon. This embeds the file in the selected location as an icon and the user can double click on the icon to open the file. The same can be done through automation.

The range supposed to set at the required place and the same has to be selected (range can be set by any of the means mentioned above). Now with the selection, the file can be embedded.

  3. Object oIconLabel = "File Name";  
  6. //ELSE SET IT TO oMissing VALUE  
  7. Object oIconFileName = "C:\\Document and Settings\\IconFile.ico";  
  9. Object oBookMark = "My_Custom_BookMark";  
  11. Object oFileDesignInfo = "C:\\Document and Settings\\somefile.doc";  
  13. Object oClassType = "Word.Document.8";  
  14. Object oTrue = true;  
  15. Object oFalse = false;  
  16. Object oMissing = System.Reflection.Missing.Value;  
  18. oWordDoc.Bookmarks.get_Item(ref oBookMark).Range.InlineShapes.AddOLEObject(  
  19.     ref oClassType,ref oFileDesignInfo,ref oFalse, ref oTrue, ref oIconFileName,  
  20.     ref oMissing,ref oIconLabel, ref oMissing);   

8. Inserting a Document File

Contents of a Word documents can also be inserted into the current document from the application by doing the following.

Insert -> File -> Select the File. This extracts the contents from the selected file and inserts it into the current document.

In automation, we need to follow a similar approach by placing the range at the required point and selecting it and then inserting the file.

  2. String oFilePath = "C:\\Document and Settings\\somefile.doc";  
  3. oWordDoc.Bookmarks.get_Item(ref oBookMark).Range.InsertFile(oFilePath,ref oMissing, ref oFalse, ref oFalse, ref oFalse);  
9. Including Water Marks/Pictures in the Document Background

Including watermarks is one other important feature for any official documents as the watermark may have the company's logo, draft logo or any other picture/text. This is useful when we want a picture or some text to be present throughout the document in the background.

We insert a watermark in the application by performing the following tasks.

Format -> Background -> Printed Watermarks

The same can also be done programmatically; moreover as we manually define the values like the angle of tilt and actual location of the watermark, we have more flexibility in defining the exact location of the watermark.

9.1 Embedding Pictures in Document Header

  3. oWord.ActiveWindow.ActivePane.View.SeekView = Word.WdSeekView.wdSeekCurrentPageHeader;  
  6. Word.Shape logoCustom = null;  
  8. String logoPath = "C:\\Document and Settings\\MyLogo.jpg";  
  9. logoCustom = oWord.Selection.HeaderFooter.Shapes.AddPicture(logoPath,  
  10.     ref oFalse, ref oTrue, ref oMissing, ref oMissing, ref oMissing, ref oMissing, ref oMissing);  
  11. logoCustom.Select(ref oMissing);  
  12. logoCustom.Name = "CustomLogo";  
  13. logoCustom.Left = (float)Word.WdShapePosition.wdShapeLeft;  
  15. oWord.ActiveWindow.ActivePane.View.SeekView = Word.WdSeekView.wdSeekMainDocument;   

9.2 Inserting Text in the Centre of the Document as Water Mark

  3. Word.Shape logoWatermark = null;  
  5. logoWatermark = oWord.Selection.HeaderFooter.Shapes.AddTextEffect(  
  6.     Microsoft.Office.Core.MsoPresetTextEffect.msoTextEffect1,  
  7.     "Enter The Text Here""Arial", (float)60,  
  8.     Microsoft.Office.Core.MsoTriState.msoTrue,  
  9.     Microsoft.Office.Core.MsoTriState.msoFalse,  
  10.     0, 0, ref oMissing);   
  11. logoWatermark.Select(ref oMissing);  
  12. logoWatermark.Fill.Visible = Microsoft.Office.Core.MsoTriState.msoTrue;  
  13. logoWatermark.Line.Visible = Microsoft.Office.Core.MsoTriState.msoFalse;  
  14. logoWatermark.Fill.Solid();  
  15. logoWatermark.Fill.ForeColor.RGB = (Int32)Word.WdColor.wdColorGray30;  
  16. logoWatermark.RelativeHorizontalPosition = Word.WdRelativeHorizontalPosition.wdRelativeHorizontalPositionMargin;  
  17. logoWatermark.RelativeVerticalPosition = Word.WdRelativeVerticalPosition.wdRelativeVerticalPositionMargin;  
  18. logoWatermark.Left = (float)Word.WdShapePosition.wdShapeCenter;  
  19. logoWatermark.Top = (float)Word.WdShapePosition.wdShapeCenter;  
  20. logoWatermark.Height = oWord.InchesToPoints(2.4f);  
  21. logoWatermark.Width = oWord.InchesToPoints(6f);  
  23. oWord.ActiveWindow.ActivePane.View.SeekView = Word.WdSeekView.wdSeekMainDocument;  
9.3 Inserting Text in the Centre of Page, and rotating it by 90 Degrees
  2. Word.Shape midRightText;  
  3. midRightText = oWord.Selection.HeaderFooter.Shapes.AddTextEffect(  
  4.     Microsoft.Office.Core.MsoPresetTextEffect.msoTextEffect1,  
  5.     "Text Goes Here""Arial", (float)10,  
  6.     Microsoft.Office.Core.MsoTriState.msoTrue,  
  7.     Microsoft.Office.Core.MsoTriState.msoFalse,  
  8.     0, 0, ref oMissing);  
  10. midRightText.Select(ref oMissing);  
  11. midRightText.Name = "PowerPlusWaterMarkObject2";  
  12. midRightText.Fill.Visible = Microsoft.Office.Core.MsoTriState.msoTrue;  
  13. midRightText.Line.Visible = Microsoft.Office.Core.MsoTriState.msoFalse;  
  14. midRightText.Fill.Solid();  
  15. midRightText.Fill.ForeColor.RGB = (int)Word.WdColor.wdColorGray375;  
  17. midRightText.Rotation = (float)90;  
  18. midRightText.RelativeHorizontalPosition =  
  19.     Word.WdRelativeHorizontalPosition.wdRelativeHorizontalPositionMargin;  
  20. midRightText.RelativeVerticalPosition =  
  21.     Word.WdRelativeVerticalPosition.wdRelativeVerticalPositionMargin;  
  22. midRightText.Top = (float)Word.WdShapePosition.wdShapeCenter;  
  23. midRightText.Left = (float)480;  
10.Including Page Numbers in Page Footer

Including auto-generated page numbers in the Footer is yet another useful feature which can be simulated in the code.

  2. oWord.ActiveWindow.ActivePane.View.SeekView = Word.WdSeekView.wdSeekCurrentPageFooter;  
  4. oWord.Selection.TypeParagraph();  
  5. String docNumber = "1";  
  6. String revisionNumber = "0";  
  8. oWord.Selection.Paragraphs.Alignment = Word.WdParagraphAlignment.wdAlignParagraphLeft;  
  9. oWord.ActiveWindow.Selection.Font.Name = "Arial";  
  10. oWord.ActiveWindow.Selection.Font.Size = 8;  
  11. oWord.ActiveWindow.Selection.TypeText("Document #: " + docNumber + " - Revision #: " + revisionNumber);  
  13. oWord.ActiveWindow.Selection.TypeText("\t");  
  14. oWord.ActiveWindow.Selection.TypeText("\t");  
  15. oWord.ActiveWindow.Selection.TypeText("Page ");  
  16. Object CurrentPage = Word.WdFieldType.wdFieldPage;  
  17. oWord.ActiveWindow.Selection.Fields.Add(oWord.Selection.Range, ref CurrentPage, ref oMissing, ref oMissing);  
  18. oWord.ActiveWindow.Selection.TypeText(" of ");  
  19. Object TotalPages = Word.WdFieldType.wdFieldNumPages;  
  20. oWord.ActiveWindow.Selection.Fields.Add(oWord.Selection.Range, ref TotalPages, ref oMissing, ref oMissing);  
  22. oWord.ActiveWindow.ActivePane.View.SeekView = Word.WdSeekView.wdSeekMainDocument;  
11. Basic Text Formatting Options

11.1 Paragraph Break

This is equivalent to hitting the enter button in the document. 

  2. oWord.Selection.TypeParagraph();

11.2 Text Formatting Option

All the text formatting options available in the Word Application can also be replicated through automation.

  2. oWord.Selection.Font.Bold = 1;  
  3. oWord.Selection.Font.Color = Word.WdColor.wdColorAqua;  
  4. oWord.Selection.Font.Italic = 1;  
  5. oWord.Selection.Font.Underline = Word.WdUnderline.wdUnderlineDashHeavy;  
11.3 Clear Formatting

When the Formatting is applied to a selection, then the same formatting gets carried on to the next lines, in order to clear the formatting, the next line needs to be selected and ClearFormatting() method needs to be called.

  2. oWord.Selection.ClearFormatting();  
12. Table of Contents

Table of Contents is very handy when it comes to official documents or some technical papers which span across many pages. Table of contents can be inserted and updated on the fly as the document gets built.

For the Table of Contents to get auto generated without any hassles, it is vital that the Headings, Sub-Headings and the Body text have their respective attributes set. When we work on the application, the values get set by themselves, we only need to edit if required. But while programming its mandatory that we set the values in the code in order to prevent any anomalies when the Table of Contents gets updated.

Below is an example of a document which was programmatically generated.

Figure 6.

It is apparent that the Header 2 and Header 3 and Body are formatted differently and even in the Table of Contents the Header 2 is slightly offset from the Header 1.

Open the above document and Outlining Tool bar, View -> Toolbars -> Outlining. And on moving the cursor on the Sample Header 2, we can see that the Format is Heading 2 and Outlining level is Level 2.

Figure 7.

And for Body, the Format is Normal + Arial, 10 pt and Outlining Level is Body text.

Figure 8.

The same values needs to be set programmatically for the Table of Contents to get generated.

12.1 Section Format

For setting the Format of the Selection, select the entire text (select between bookmarks like mentioned before in Selection section) and set the value

  3. Object styleHeading2 = "Heading 2";  
  4. Object styleHeading3 = "Heading 3";  
  5. oWord.Selection.Range.set_Style(ref styleHeading2);  
  6. oWord.Selection.Range.set_Style(ref styleHeading3);  
12.2 Outline Level

For setting the outline level, select the contents and set it to one of the values mentioned below

  3. //SET THE VALUE  
  4. oWord.Selection.Paragraphs.OutlineLevel =Word.WdOutlineLevel.wdOutlineLevel2;                                            
  5. oWord.Selection.Paragraphs.OutlineLevel = Word.WdOutlineLevel.wdOutlineLevel3;          
  6. oWord.Selection.Paragraphs.OutlineLevel = Word.WdOutlineLevel.wdOutlineLevelBodyText;   
12.3: Inserting Table of Contents

Once the Outline Levels & Section Style are set, the Table of Contents can be inserted programmatically and the page numbers gets populated automatically based on the Outline Levels & Section Style set by the user. (Also refer this MSDN Link)

  3. Object oBookmarkTOC = "Bookmark_TOC";  
  5. Word.Range rngTOC = oWordDoc.Bookmarks.get_Item(ref oBookmarkTOC).Range;  
  7. rngTOC.Select();  
  9. Object oUpperHeadingLevel = "1";  
  10. Object oLowerHeadingLevel = "3";  
  11. Object oTOCTableID = "TableOfContents";  
  12. oWordDoc.TablesOfContents.Add(rngTOC, ref oTrue, ref oUpperHeadingLevel,  
  13.     ref oLowerHeadingLevel,ref oMissing, ref oTOCTableID, ref oTrue,  
  14.     ref oTrue, ref oMissing, ref oTrue, ref oTrue, ref oTrue);  
12.4 Updating Table of Contents

Usually the Table of Contents is inserted in the beginning of the document generation and once all the contents are populated, the locations of the Headings and Sub Headings tend to change. If the Table of Contents is not updated, then its contents points to different pages. To overcome this hassle, the Table of Contents needs to be updated at the end of the Automation.

  2. oWordDoc.TablesOfContents[1].Update();  
  4. oWordDoc.TablesOfContents[1].UpdatePageNumbers();  
13. Saving/Closing & Re-Opening the File

13.1 Saving the File

  2. Object oSaveAsFile = (Object)"C:\\SampleDoc.doc";  
  3. oWordDoc.SaveAs(ref oSaveAsFile, ref oMissing, ref oMissing, ref oMissing,  
  4.     ref oMissing, ref oMissing,ref oMissing, ref oMissing, ref oMissing,  
  5.     ref oMissing, ref oMissing, ref oMissing, ref oMissing, ref oMissing,  
  6.     ref oMissing, ref oMissing);  
13.2 Closing the File
  2. oWordDoc.Close(ref oFalse, ref oMissing, ref oMissing);  
  4. oWord.Quit(ref oMissing, ref oMissing, ref oMissing);  
13.3 Re-Opening the File

The Open () method which we use in Word2003 dll might throw an exception if the client have another version of word installed in their machine. If the client has Word 2002, then he has to open a word file only by Open2002 () method. Open () method which comes for Word 2003 might through an exception in Word 2002 environment.  And for Word 2000, there is a method called Open2000 () and Open2002 () for Office 2002 and so on. So it is wise to put the Open () in a try-catch block as mentioned below.

Figure 10.

14. Tips for Word Automation to Create New Document (Non-Base Template Approach)

(Refer to this MSDN link)

When we proceed to create a New Document without using the Base Template, the most useful entity is the inbuilt Bookmark endofdoc. It would be a build-from-scratch approach where the programmer starts of the automation by inserting his first section of contents, then setting the range to point to the endofdoc Bookmark and selecting it and inserting his contents and again selecting the endofdoc which would be pointing to the end of the document which would now be after the two sections.