Excel Object Model Overview
To develop solutions that use Microsoft Office Excel, you can interact with the objects provided by the Excel object model. This topic introduces the most important objects:
Applies to: The information in this topic applies to document-level projects and VSTO add-in projects for Excel. For more information, see Features Available by Office Application and Project Type.
The object model closely follows the user interface. The Application object represents the entire application, and each Workbook object contains a collection of Worksheet objects. From there, the major abstraction that represents cells is the Range object, which enables you to work with individual cells or groups of cells.
In addition to the Excel object model, Office projects in Visual Studio provide host items and host controls that extend some objects in the Excel object model. Host items and host controls behave like the Excel objects they extend, but they also have additional functionality such as data-binding capabilities and extra events. For more information, see Automating Excel by Using Extended Objects and Host Items and Host Controls Overview.
This topic provides a brief overview of the Excel object model. For resources where you can learn more about the entire Excel object model, see Using the Excel Object Model Documentation.
For a related video demonstration, see How Do I: Use Event Handlers in an Excel 2007 Add-in?, and How Do I: Use Shapes to Create a Bubble Chart in Excel?.
When you create a new VSTO Add-in project for Excel, Visual Studio automatically creates a ThisAddIn.vb or ThisAddIn.cs code file. You can access the Application object by using Me.Application or this.Application.
When you create a new document-level project for Excel, you have the option of creating a new Excel Workbook or Excel Template project. Visual Studio automatically creates the following code files in your new Excel project for both workbook and template projects.
You can use the Globals class in your project to access ThisWorkbook, Sheet1, Sheet2, or Sheet3 from outside of the respective class. For more information, see Global Access to Objects in Office Projects. The following example calls the PrintPreview method of Sheet1 regardless of whether the code is placed in one of the Sheetn classes or the ThisWorkbook class.
Because the data in an Excel document is highly structured, the object model is hierarchical and straightforward. Excel provides hundreds of objects with which you might want to interact, but you can get a good start on the object model by focusing on a very small subset of the available objects. These objects include the following four:
Much of the work done with Excel centers around these four objects and their members.
The Excel Application object represents the Excel application itself. The Application object exposes a great deal of information about the running application, the options applied to that instance, and the current user objects open within the instance.
The Microsoft.Office.Interop.Excel.Workbook object represents a single workbook within the Excel application.
The Office development tools in Visual Studio extends the Microsoft.Office.Interop.Excel.Workbook object by providing the Microsoft.Office.Tools.Excel.Workbook type. This type gives you access to all features of a Microsoft.Office.Interop.Excel.Workbook object. For more information, see Workbook Host Item.
The Microsoft.Office.Interop.Excel.Worksheet object is a member of the Worksheets collection. Many of the properties, methods, and events of the Microsoft.Office.Interop.Excel.Worksheet are identical or similar to members provided by the Application or Microsoft.Office.Interop.Excel.Workbook objects.
Excel provides a Sheets collection as a property of a Microsoft.Office.Interop.Excel.Workbook object. Each member of the Sheets collection is either a Microsoft.Office.Interop.Excel.Worksheet or a Microsoft.Office.Interop.Excel.Chart object.
The Office development tools in Visual Studio extend the Microsoft.Office.Interop.Excel.Worksheet object by providing the Microsoft.Office.Tools.Excel.Worksheet type. This type gives you access to all features of a Microsoft.Office.Interop.Excel.Worksheet object, as well as new features such as the ability to host managed controls and handle new events. For more information, see Worksheet Host Item.
The Microsoft.Office.Interop.Excel.Range object is the object you will use most within your Excel applications. Before you can manipulate any region within Excel, you must express it as a Range object and work with methods and properties of that range. A Range object represents a cell, a row, a column, a selection of cells that contains one or more blocks of cells, which might or might not be contiguous, or even a group of cells on multiple sheets.
Visual Studio extends the Microsoft.Office.Interop.Excel.Range object by providing the Microsoft.Office.Tools.Excel.NamedRange and Microsoft.Office.Tools.Excel.XmlMappedRange types. These types have most of the same features as a Microsoft.Office.Interop.Excel.Range object, as well as new features such as the data binding capability and new events. For more information, see NamedRange Control and XmlMappedRange Control.
For complete information about the Excel object model, you can refer to the Excel primary interop assembly (PIA) reference and the VBA object model reference.
The Excel PIA reference documentation describes the types in the primary interop assembly for Excel. This documentation is available from the following location: Excel 2010 Primary Interop Assembly Reference.
For more information about the design of the Excel PIA, such as the differences between classes and interfaces in the PIA and how events in the PIA are implemented, see Overview of Classes and Interfaces in the Office Primary Interop Assemblies.
The VBA object model reference documents the Excel object model as it is exposed to Visual Basic for Applications (VBA) code. For more information, see Excel 2010 Object Model Reference.
All of the objects and members in the VBA object model reference correspond to types and members in the Excel PIA. For example, the Worksheet object in the VBA object model reference corresponds to the Microsoft.Office.Interop.Excel.Worksheet object in the Excel PIA. Although the VBA object model reference provides code examples for most properties, methods, and events, you must translate the VBA code in this reference to Visual Basic or Visual C# if you want to use them in an Excel project that you create by using Visual Studio.
Explains how you can create document-level customizations and VSTO Add-ins for Microsoft Office Excel.
Provides examples that show how to perform common tasks with ranges.
Provides examples that show how to perform common tasks with worksheets.
Provides examples that show how to perform common tasks with workbooks.