I’m going to start off my first “How Do I” post with a simple application that exports the application’s data to a Word Mailing Label Document. At the end of the blog you’ll find links to the the VS LightSwitch project code for both C# and VB.Net.
I was sending several dozen birth announcements recently to friends and family, and realized that I needed a better way to manage all the addresses and contact information I had floating around my house. That, and needing to brush up on my Visual Studio LightSwitch (LS) skills, led to the creation of a Contacts manager application.
I was able to quickly create an application using LS which I thought would meet everyone’s needs. But my wife insisted she wasn’t interested in using it unless it could export all the contact information to a Word Document. Fortunately, I was able to get a start on figuring out how to add this functionality by reading Beth Massi’s blog post on creating reports in Word for LS.
Using the System.Runtime.InteropServices.Automation.AutomationFactory class I was able to do just what I needed all from the Client side.
So let’s get started creating a very basic application to manage our contacts, then add some functionality to create a mailing label document using the COM Object and the AutomationFactory class..
Step 1 – Create our simple Contacts table and screen
- Create a Visual Studio LightSwitch C# or VB Project
- Add a table – Contact, with the following properties:
- FirstName | String | Required
- MiddleName | String
- LastName | String | Required
- AddressLine1 | String
- AddressLine2 | String
- City | String
- State | String
- ZipCode | String
- Country | String
- PhoneNumber1 | PhoneNumber
- PhoneNumber2 | PhoneNumber
- BirthDate | Date
- MiscellaneousInformation | String
- Add a List and Details screen, called Contacts, which uses the Contacts table data
- OPTIONAL - I made some minor changes to the “List” portion of the screen
- In the screen designer, navigate to Columns Layout-> Rows Layout –> List and change “List” to “Data Grid” using the drop down arrow
- Under Columns Layout –> Rows Layout –> Data Grid –> Data Grid Row remove all fields except for “First Name” and “Last Name”
- In the screen designer, under Columns Layout –> Screen Command Bar add a button
- Call the button “Export to Word Mailing Label Document” (we’ll add the code later)
- Your screen designer and Solution Explorer should look something like this now:
Step 2 – Add Client side code to generate our Word document
- In Solution Explorer, click the drop down arrow next to the “Logical View” button and select “File View”
- We are going to add our own User Class to the Client project, so right click the Client project, and select Add –> Class.
- Add a new Class called ExportToWord. Paste the below code into the class:
//' Copyright © Microsoft Corporation. All Rights Reserved.
//' This code released under the terms of the
//' Microsoft Public License (MS-PL, http://opensource.org/licenses/ms-pl.html)
/// Create a mailing label document based upon our Contacts and their corresponding address information
/// <returns>A byte array containing the generated Word Mailing Label Document</returns>
public static byte ExportToMailingLabelDocumentWithCOM()
Object fileName = String.Concat(
@"\Contacts_" + System.DateTime.UtcNow.ToFileTimeUtc() + ".docx");
Object labelName = "8660 Easy Peel Address Labels";
dynamic wordObject = System.Runtime.InteropServices.Automation.AutomationFactory.CreateObject("Word.Application");
// Create an empty mailing label document
dynamic mailingLabelDoc = wordObject.MailingLabel.CreateNewDocument(ref labelName);
// Format the contacts address information
List<string> contacts = FormatContactsAddressInformation();
// Populate the word document with labels
// Save our label doc as the default word format (i.e. docx)
catch (Exception e)
throw new InvalidOperationException("Failed to create document", e);
// Wait for Word to shut down to ensure the document is released
if (mailingLabelDoc != null)
if (wordObject != null)
// Cast our wordObject as IDisposable so that we can
// invoke .Dispose() and be sure the COM object is released
IDisposable disposable = wordObject as IDisposable;
if (disposable != null)
// Take our newly created word document, and stick into our a Byte array
byte buffer = File.ReadAllBytes((string)fileName);
// Delete the file now that we are done with it
// We'll pass back the byte buffer and let the user choose a filename and location
/// Formats each contacts address information and stores the data into a List
private static List<string> FormatContactsAddressInformation()
// Populate a List with our contacts and their address information
List<string> contacts = new List<string>();
EntitySet<Contact> contactsSet = Application.Current.CreateDataWorkspace().ApplicationData.Contacts;
foreach (Contact contact in contactsSet.OrderBy(x => x.LastName))
string formattedAddress = contact.FirstName + " " + contact.LastName + Environment.NewLine + contact.AddressLine1 + Environment.NewLine;
formattedAddress += contact.AddressLine2 + Environment.NewLine;
formattedAddress += contact.City + " " + contact.State + " " + contact.ZipCode + Environment.NewLine;
formattedAddress += contact.Country;
/// Populate the Labels in a given word document with our Contact's information
private static void PopulateLabels(List<string> contacts, dynamic wordDocument)
dynamic docTable = wordDocument.Tables;
// Starting at row 1, iterate through each row and column in the Mailing Label's Table
// And for each cell, insert our Contact's address information
int row = 1;
int currentContactIndex = 0;
while (currentContactIndex < contacts.Count)
// Skip even numbered columns since they are "divider" columns and not intended for cell text
for (int column = 1; column <= docTable.Columns.Count; column += 2)
// If we've run out of Contacts, break out
if (currentContactIndex >= contacts.Count)
docTable.Cell(row, column).Range.Text = contacts[currentContactIndex];
docTable.Cell(row, column).Range.ParagraphFormat.Alignment = 1;
docTable.Cell(row, column).Range.Cells.VerticalAlignment = 1;
docTable.Cell(row, column).Range.Rows.Alignment = 1;
// Keep track of what row we are on in our table
// Check to see if we've run out of rows in our table
if (row > docTable.Rows.Count)
// Add a new row to our table
- Here’s the breakdown of what the ExportToWord’s class methods are doing:
- Iterates over the table cell’s in a Word document instance.
- Populates each cell with a Contact’s address information.
- Iterates over each Contact in the SQL database, ordering the contacts by LastName .
- Takes the necessary address information from each contact and formats it into a nice looking string.
- Each string is added to a List of address information.
- Creates a Word.Application COM Object.
- Creates an empty Mailing Label Document based off the “8660 Easy Peel Address Labels” template.
- Calls FormatContactsAddressInformation() and PopulateLabels()
- Now the mailing labels are populated with the correct data
- Save the document and then store it in a byte array
- Delete the original document, and pass the byte array back to the calling method
Step 4 – Add Button code to call into our ExportToWord class
- We are now going to add code to our button to invoke the code we added in the previous steps.
- In the screen designer, under Columns Layout –> Screen Command Bar, right click the “Export to Word Mailing Label Document” button and select “Edit Execute code”
- Paste the following code into the your button’s method :
// Call into our Client User Class to create the word document, then return it as a byte array
byte wordDocument = ExportToWord.ExportToMailingLabelDocumentWithCOM();
- This won’t compile now until we add the DisplaySaveAsFileDialog() method to the same class as well. So copy and paste the below method into the class:
/// This method will display a SaveAsFileDialog to the user to save
/// a given file buffer
private void DisplaySaveAsFileDialog(byte fileBuffer)
// Need to switch back to the Main UI thread before we can pop up any dialogs.
// We need to do this, because by default the button code operates outside of the main
// UI thread, and the only way the user is going to see a Dialog box is for it to
// appear inside the main UI thread.
SaveFileDialog dialog = new SaveFileDialog();
dialog.DefaultExt = ".docx";
bool dialogResult = (bool)dialog.ShowDialog();
if (dialogResult == true)
using (FileStream fileStream = (FileStream)dialog.OpenFile())
fileStream.Write(fileBuffer, 0, fileBuffer.Length);
- And then, we will need to add these using statements.
//Namespace of our ExportToWord class
- In addition to invoking the ExportToWord.ExportToMailingLabelDocumentWithCOM() method we wrote, this button code will display a Save File Dialog so that the user can decide where on their client side machine they want to save the Word document.
- To create the file, the Save File Dialog will read in the byte array which we returned earlier from the ExportToMailingLabelDocumentWithCOM() method.
- As the code comments in DisplaySaveAsFileDialog() state, to invoke the Save File Dialog, we have to switch to the main UI thread since the button’s code operates outside the main UI thread. And if we want to do something like pop up a dialog, it has to be done in the main UI thread.
Step 6 – Run it
- Compile and run our Contacts application now.
- Enter in some Contact information.
- We should have a screen looking something like this:
- Now if we click the “Export to Word Mailing Label Document” button, our application will display a “Save As” File dialog.
- After specifying a name for our file, we should be able to open it and see our mailing labels.
- I specified the 8660 Easy Peel Address Labels in our code when generating the Word document, but you could customize this code for a different mailing label template if needed.
Code samples are here: http://code.msdn.microsoft.com/Visual-Studio-LightSwitch-d2ca025e
In the near future I should have another blog post on how to create a document on the Server side (allowing you to take advantage of Intellisense) and transfer that document back to the Client.
Let me know if you have any questions!
Thanks - Matt Sampson