Tools for office c#

CreateSmartTag method. For more information about Globals. Factory , see Global access to objects in Office projects. Because the object model of the Office extensions for the. NET Framework 4 or later are based on interfaces, you can use the type equivalence feature in both Visual C and Visual Basic in Visual Studio to embed type information from the Visual Studio Tools for Office runtime into your solution.

This feature enables Office solutions and the Visual Studio Tools for Office runtime to version independently of each other. For example, if your solution uses the Document interface as an embedded type and the next version of the runtime adds members to the Document interface, your solution will still work with the next version of the runtime. If your solution does not use the Document interface as an embedded type, then your solution will no longer work with the next version of the runtime.

By default, the type equivalence feature is not enabled when you create an Office project that targets the. If you want to enable this feature, set the Embed Interop Types property of any of the following assembly references in your project to True :.

After you make this change, type information for all of the runtime types used by the project is embedded into the solution assembly when you build the project. This embedded type information, rather than the type information in the referenced assemblies, are used by the solution at run time. Although you should never have to work with these DLLs directly, knowing the purposes of these DLLs can help you better understand the architecture of Office solutions.

For information about how these components are used during the load process, see Architecture of document-level customizations and Architecture of VSTO Add-ins. For more information about the different versions of the Visual Studio Tools for Office runtime that can be used for other solutions, see Run solutions in different versions of Microsoft Office.

It loads the version of the Office extensions for the. NET Framework that is required by the solution. It implements the IDTExtensibility2 interface. It implements the IManagedAddin interface. For more information, see IManagedAddin interface.

There are separate bit and bit versions of the Visual Studio Tools for Office runtime. These versions of the runtime are used to run solutions in bit and bit editions Office. The following table shows which version of the runtime is required for each combination of Windows and Office. When you install Office, the required version of the Visual Studio Tools for Office runtime is installed along with Office. For example, when you install the bit edition of Office on a bit version of Windows, the bit version of the Visual Studio Tools for Office runtime is also installed.

The bit version of Office can also run Office solutions that were created by using project templates for the Microsoft Office system in Visual Studio These assemblies ensure that the correct version of the primary interop assemblies is loaded at run time. For example, when a solution that references a Office assembly runs on a computer that has the Office version of the same primary interop assembly, the binding redirect assembly instructs the.

NET Framework runtime to load the Office version of the primary interop assembly. For more information, see How to: Enable and disable automatic binding redirection. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? Note Interested in developing solutions that extend the Office experience across multiple platforms?

Note Some assemblies are added to a project automatically when an assembly that references them is added. Submit and view feedback for This product This page. View all page feedback. In this article. Microsoft Office Microsoft Graph Microsoft Smart Tags 2. Interested in developing solutions that extend the Office experience across multiple platforms?

Check out the new Office Add-ins model. Describes the new design of Office projects that target the. NET Framework 4 or later, and lists breaking changes to code in Office projects that you migrate to the.

NET Framework 4 or later. Describes which applications and projects are required to use Office development features such as Ribbon extensibility, custom task panes, actions panes, and form regions. Provides information and steps for installing the Office development tools, the runtime that enables Office solutions to run on end-user computers, and the Office primary interop assemblies. Provides a summary of the important concepts needed to use Visual Studio to create document-level customizations for Excel.

Provides a summary of the important concepts needed to use Visual Studio to create document-level customizations for Word.