#Installing microsoft open xml converter generator
#Installing microsoft open xml converter code

First, make sure Outlook desktop is closed.You can sideload the add-in using the Teams Toolkit or in a command prompt, bash shell, or terminal.

#Installing microsoft open xml converter code

Sideload the add-in in Visual Studio Code Close the original Visual Studio Code window. It then opens the project in a second Visual Studio Code window. Teams Toolkit creates the project with your source files and scaffolding. In the Application name dialog, give a name to the project (with no spaces). In the Workspace folder dialog, select the folder where you want to put the converted project. In the Select import project manifest file drop down, browse to the XML manifest file. In the Existing add-in project folder drop down, browse to the root folder of the add-in project. In the App Features Using an Outlook Add-in drop down, select Import an Existing Outlook Add-in. In the New Project drop down, select Outlook Add-in. Open Visual Studio Code and select the Teams Toolkit icon on the Activity Bar. Import the add-in project to Teams Toolkit The easiest way to convert is to use Teams Toolkit.

#Installing microsoft open xml converter generator

NodeJS and npm projects that aren't created with Yeoman Generator.Projects created with the Office Yeoman Generator (aka 'Yo Office').

There are several ways to carry out the remaining tasks, depending on the IDE and other tools you want to use for your project, and on the tool you used to create the project. When you've added the files to the project, add and (in that order) to the XML manifest just below the element. For guidance, see Create an icon for your add-in. These are required for an add-in that uses the unified manifest, so you need to create them if the project doesn't already have them. Because these are both optional elements, your add-in project mignt not have one or both. They're specified in the IconUrl and HighResolutionIconUrl elements in the XML manifest. It's highly likely that you have the two image files already in your add-in.

If you created the project with Teams Toolkit or with the 'unified manifest' option in the Office Yeoman Generator, it already uses the unified manifest.

Projects created in Visual Studio, as distinct from Visual Studio Code, can't be converted at this time.

Add-ins that use the unified manifest can be sideloaded only on Office version 1.10000 or later.

The unified manifest is a preview feature for Office Add-ins and is currently supported only for Outlook on Windows.