![]() ![]() For example, you can use the Globals class to call code in the ThisAddIn class from an event handler of a Ribbon button in a VSTO Add-in.įor more information, see Global access to objects in Office projects. You can access these objects from any code in your project by using the Globals class. When an Office solution is loaded, the Visual Studio Tools for Office runtime instantiates each of the generated classes in your project. For more information, see Events in Office projects. To clean up resources used by your VSTO Add-in, you can add code to the Shutdown event handler. To initialize your VSTO Add-in, you can add code to the Startup event handler. To get started writing code, you typically add code to these event handlers. ![]() For more information, see Program VSTO Add-ins.Īll generated classes in Office projects include Startup and Shutdown event handlers. Instead, this class represents the VSTO Add-in itself, and it provides members you can use to access the object model of the host application and access other features available to VSTO Add-ins. This class does not resemble a class in the host application's object model. VSTO Add-in projects provide a generated class called ThisAddIn. For more information about the generated classes in document-level projects, see Program document-level customizations. For example, the generated ThisDocument class in a Word document project provides the same members as the Document class in the Word object model. In document-level projects for Excel and Word, the generated class resembles a top-level object in the application's object model. These classes also provide access to the object model of the host application and access to features like actions panes and custom task panes. For more information, see the following topics:Īll Office projects include one or more generated classes that provide the entry point for your code. For example, the way you call methods that have optional parameters in an Office primary interop assembly depends on the programming language you are using in your project. For an overview of the types in the Office PIAs, see Overview of classes and interfaces in the Office primary interop assemblies.īecause the types in the Office PIAs correspond to types in the COM-based object models, the way you use these types is often different from other managed types. The Office PIAs contain a combination of types that expose the object model of the Office applications and additional infrastructure types that are not intended to be used directly in your code. For more information, see Design and create Office solutions. The Office PIAs are not required on end-user computers to run Office solutions that target the. For more information, see Configure a computer to develop Office solutions. You must have the Office PIAs installed and registered in the global assembly cache on your development computer to perform most development tasks. Use primary interop assemblies at design time and runtime For more information, see How to: Target Office applications through primary interop assemblies. To automate the features of other Office applications from the project, you must add a reference to the appropriate PIA manually. When you create an Office project in Visual Studio, a reference to the appropriate PIA is automatically added to the project. The primary interop assemblies enable managed code to interact with the COM-based object model of the Office applications.Įvery Microsoft Office application has a PIA. To automate Office applications by using managed code, you must use the Office primary interop assemblies (PIAs). ![]() However, you cannot use managed code (such as Visual Basic or C#) directly to automate Office applications. Microsoft Office applications expose much of their functionality to Automation. Automation enables you to use code to create and control software objects exposed by any application, DLL, or ActiveX control that supports the appropriate programmatic interfaces. The key technology that makes creating an integrated Microsoft Office solution possible is Automation, which is part of the Component Object Model (COM) technology. See Features available by Office application and project type. Other differences are related to the design of Office projects.Īpplies to: The information in this topic applies to document-level projects and VSTO Add-in projects. Many of these differences are related to the way the Office object models are exposed to managed code. There are some aspects of writing code in Office projects that are different from other types of projects in Visual Studio. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |