How does Microsoft's decision to remove Custom XML affect this method of document injection? I have a working solution very popular with my customers based on the ideas presented in this post and others. I do not know what my options are now that Custom XML is to be removed? I would imagine that Content Controls are here to stay... the question is "what can I bind them to if not Custom XML"?

http://www.computerworld.com/s/article/9142627/Microsoft_yanks_Custom_XML_from_Word_offers_patch_to_OEMs?taxonomyId=1