Good question. There is no API method to automate it 😃
Two possible directions that come to mind are either use some automation tool that emulates the user behavior either check if extension properties is stored in xml within prj folder.
I should clarify my scenario. I want a Document Extension to be in every document on the Test Server, but not the Prod Server. So I would prefer to not actually update the Document properties. My preference would be to add the extension at runtime. I'm thinking of updating opendoc.htm and wondering if there was any experience with this.
The document extension needs to be installed on Prod to be able to be used by the application.. so what if you just leave it out on prod and have it only installed on test? Alternatively disable Extensions in the security settings, but this might interfere with any other extensions deployed..
My plan at this point is to have a copy of the Extension that does nothing -- a NoOp -- on the Prod Server. The test server will have active code. I will just have to add the extension to every document properties.
I would prefer to inject it the server level, but there doesn't appear to be a supported method to do that.
.png "Luminary Alumni"){kind=icon}
