locked
How can I open the Outlook Add-in XML manifest in Manifest Designer? RRS feed

  • Question

  • In the documentation for the Outlook Add-in it mentions that it's XML manifest can be opened in Manifest Designer. When I follow the steps it only opens in plain text editor. 

    What could I be missing or what could I be doing wrong? 

    Screen shot: http://s32.postimg.org/er7ldo3id/Screen_Clip_29.png

    Documentation: https://dev.office.com/docs/add-ins/get-started/create-and-debug-office-add-ins-in-visual-studio

    Thursday, May 12, 2016 1:32 AM

Answers

  • Double click on xml will open it in the editor. Double click on its parent which is OutlookWebAddin1Manifest (in your screenshot) then it will open the manifest designer.

    The documentation (https://dev.office.com/docs/add-ins/get-started/create-and-debug-office-add-ins-in-visual-studio) also says the same:

    "To modify the settings of your add-in, open the  Manifest Designer. The Manifest Designer is a property page-like editor that enables you to modify the most common settings of your add-in in a more visual way. To open the  Manifest Designer from Solution Explorer, expand the "Office" add-in project node, choose the folder that contains the XML manifest, and then press the ENTER key."

    Thursday, May 12, 2016 11:25 PM

All replies

  • Double click on xml will open it in the editor. Double click on its parent which is OutlookWebAddin1Manifest (in your screenshot) then it will open the manifest designer.

    The documentation (https://dev.office.com/docs/add-ins/get-started/create-and-debug-office-add-ins-in-visual-studio) also says the same:

    "To modify the settings of your add-in, open the  Manifest Designer. The Manifest Designer is a property page-like editor that enables you to modify the most common settings of your add-in in a more visual way. To open the  Manifest Designer from Solution Explorer, expand the "Office" add-in project node, choose the folder that contains the XML manifest, and then press the ENTER key."

    Thursday, May 12, 2016 11:25 PM
  • There is a problem with the VS2015 Community built in template for Outlook Add-In.

    Creating a New Project and choosing Outlook Add-In will result in a non-openable manifest in the designer. Just the XML will open, even with all the double click or the Enter key.

    After searching for many days, I found that the version override declaration inside the XML was the culprit. Removing the line:  xmlns:mailappor="http://schemas.microsoft.com/office/mailappversionoverrides/1.0"

    in the schema declaration at the top fix the manifest not opening issue...

    Is there a way to fix the VS template to get the manifest designer to work ?

    Jean-Paul Bleau

    • Proposed as answer by JCSvercek Sunday, June 19, 2016 10:02 PM
    Wednesday, June 8, 2016 12:38 PM
  • Expanding Jean-Paul Bleau's answer, the  xmlns:mailappor="http://schemas.microsoft.com/office/mailappversionoverrides/1.0"

     should be changed to

    xmlns:mailappor="http://schemas.microsoft.com/office/appforoffice/1.1"


    John C Svercek


    • Edited by JCSvercek Tuesday, June 21, 2016 1:11 AM
    Sunday, June 19, 2016 10:06 PM
  • Hi John,

    Thanks for your answer.

    Is this documented somewhere ?

    JP


    Jean-Paul Bleau

    Monday, June 20, 2016 1:15 PM
  • JP, If you hover over the bad link, the tool tip shows the correct link. I made the leap of faith and tried it and it worked.

    John


    John C Svercek

    Tuesday, June 21, 2016 1:17 AM
  • JP, I found documentation here.

    https://msdn.microsoft.com/en-us/library/hh642904(v=office.12).aspx

    After some reading, I am of the opinion that my solution, while displaying the Manifest Designer, may not work. Further research is warranted.

    Fei Xue, the "Answer" doesn't work. Can we get that unmarked?

    Thanks,

    John


    John C Svercek

    Tuesday, June 21, 2016 10:34 PM
  • JP, after very careful reading and rereading of the documentation I discovered a typo in the URL in question. Just remove the "/1.0 " from the URL and it will work fine. Check this link

    https://msdn.microsoft.com/en-us/library/mt486948(v=office.12).aspx

    John

    PS. How do we get MS to fix this?


    John Svercek

    Wednesday, June 22, 2016 2:07 AM