Microsoft vsto 2005 runtime

Microsoft Office YTD Video Downloader. Adobe Photoshop CC. VirtualDJ Avast Free Security. WhatsApp Messenger. Talking Tom Cat. Clash of Clans. Subway Surfers. TubeMate 3. Google Play. Canon ink cartridge. Beanie Babies movie on Apple. Twee's return on TikTok. Windows Windows. For more information, see Visual Studio Tools for Office runtime installation scenarios.

Interested in developing solutions that extend the Office experience across multiple platforms? Check out the new Office Add-ins model. You need to install the Visual Studio Tools for Office runtime on a server. For example, you want to use the ServerDocument class to manage document-level solutions on a server.

You need to install the runtime on a computer that already has all the other prerequisites for Office solutions installed. You must be an administrator on the development computer to install the. To download the. NET Framework 4, see Microsoft.

NET Framework 4. You can download these setup files from Visual Studio Tools for Office runtime. The only interfaces you can implement directly have names that begin with the letter I , such as ISmartTagExtension. All interfaces that do not begin with the letter I are implemented internally by the Visual Studio Tools for Office runtime, and these interfaces might change in future releases.

To create objects that implement these interfaces, use methods provided by the Globals. Factory object in your project. For example, to get an object that implements the SmartTag interface, use the Globals. 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.