Mar 24, 2014 at 5:18 PM
Edited Mar 25, 2014 at 9:12 PM
Specifically relative to the AMS, how do UserCustomAction's work? Do they run during the Page life-cycle every time or are they cached? Is there a tool for checking the status of how many UserCustomAction are installed on a Site? As we trend away from things
I don't have much information about the page lifecycle, profiling, but for your question:
"Is there a tool for checking the status of how many UserCustomAction are installed on a Site?"
to put a link to your app in the settings drop down to make it feel like an OOTB tool.
For more details see:
I prototyped a SharePoint-hosted app for managing user custom actions using these APIs a while back but I found that there were other apps available in the Store which looked like they already had this capability and I stopped working on it.
The only tricks I came across was to ensure that you build the CommandUI XML properly. You have to make sure to use all the *NS (NameSpace) suffixed methods to create a document instead of the normal methods in order to preserve the casing of the elements.
E.g. Use createElementNS not createElement, and use setAttributeNS not setAttribute. You can look at the XML generated by Visual Studio and this reference: Default Custom Action Locations and IDs
to determine how to construct the document. Then it's a matter of POSTing the Xml to the correct endpoint.