Using module extension in Outlook

Question

I'm creating an Outlook add-in, and I want to try out the new module extension. However, following the example from: https://dev.office.com/docs/add-ins/outlook/extension-module-outlook-add-ins, I get an error when creating the manifest.

<VersionOverrides xmlns="http://schemas.microsoft.com/office/mailappversionoverrides" xsi:type="VersionOverridesV1_0">
  <VersionOverrides xmlns="http://schemas.microsoft.com/office/mailappversionoverrides/1.1" xsi:type="VersionOverridesV1_1">
    ...
  </VersionOverrides>
</VersionOverrides>

the error occurs on the second VersionOverrides with the message:

"The element 'VersionOverrides' in namespace 'http: // schemas microsoft com/office/mailappversionoverrides' has invalid child element 'VersionOverrides' in namespace 'http:// schemas microsoft com/office/mailappversionoverrides/1.1'. List of possible elements expected: 'Description, Requirements, Hosts' in namespace 'http:// schemas microsoft com/office/mailappversionoverrides'."

since I can't post more than 2 links, I have replaced the . in the URLs with spaces.

It seems odd to me to include a versionoverride inside a versionoverride, but if I change the first one by any means, VS won't accept it as following the schema. Likewise, if I don't include the second versionoverride, VS gives the following error:

"This is an invalid xsi:type 'http:// schemas microsoft com/office/mailappversionoverrides:Module'."

The rest of the manifest i almost symmetrical to the example from officeDev, apart from elements like Title and Id.

What am I doing wrong?

Answer 1

personally, I stopped using XSD validation from Visual Studio with Addin manifest. But what you should do is updating the the XSD file for XML schema validation to support the new version overrides. Check the following resources:

• How to Select the XML Schemas to Use on MSDN
• XML Validation with XSD in Visual Studio IDE on SO
• Update the version of your JavaScript API for Office and manifest schema files on GitHub

In addition, you should take care of the following situation when using modules. Here is another example on GitHub of modules declaration.

Answer 2

You do not need Visual Studio to build the add-in manifest. The manifest is a simple XML file that you can create in notepad as well and simply upload from your manage integrations(previously manage add-ins) page.

The VS XSD may not be updated to support VO1.1. You can create the XML in VS and not worry about the VersionOverride error due to its XSD validation.

Simply go ahead and install the XML from manage integrations using Add from file option and you should be good to go!