Any disadvantages in using older XML on newer Office version?

[RandomGerman]

Hello there,

this is not a specific problem to solve, but something I want to learn about:

We all start the XML code for Office 2007 with: [CODE]<customUI xmlns="http://schemas.microsoft.com/office/2006/01/customui">[/CODE]

And in Office 2010 and onwards we start with: [CODE]<customUI xmlns="http://schemas.microsoft.com/office/2009/07/customui">[/CODE]

I know, I'm going to run into problems, using 2009/07 on a Office-2007-machine, but is there any danger of errors to do it the other way round? Is there any disadvantage of using 2006/01 on machines with 2010/2013/2016? If yes, which? If not, it would be easier to use ribbons with 2006/01 for both machines, in case you have, e.g., one with Office 2007 and one with Office 2013

I usually create PowerPoint-Addins, but this might be something important for Access, Excel, Outlook, Word, too.

Thank you for sharing your knowlegde/experiences!
RG

[Paul_Hossler]

[CODE]<customUI xmlns="http://schemas.microsoft.com/office/2006/01/customui">[/CODE]

works with Office 2016 versions




[CODE]<customUI xmlns="http://schemas.microsoft.com/office/2009/07/customui">[/CODE]

allows some additional features to be used. Backstage is one of them



It is possible (I believe) to have both sections in one file

[RandomGerman]

Thank you, Paul, this helps. As long as I don't use backstage or other new features, everything will be fine with 2006/01. It's good to know to have no disadvantages with "old" XML code.

[Paul_Hossler]

I've never found any disadvantages, but I usually keep things pretty simple and not get myself into trouble by trying to be too fancy