topic Re: licensing backstage does not show external extension in ArcGIS Pro SDK Questions

licensing backstage does not show external extension

RomanTrojan — Mon, 01 Oct 2018 17:27:48 GMT

I am evaluating the sample arcgis-pro-sdk-community-samples/Framework/Licensing/ as an Add-in that should implement the configurable extension pattern in Pro shown on the licensing tab on the ArcGIS Pro application backstage as an External Extension. Unfortunately there is no External Extension entry on the licensing tab backstage (between Esri Extensions and Settings. I cannot find any restrictions preventing the sample to achieve this issue! The sample is unchanged (including an <extensionConfig .../> element to Config.daml). Can you give me some helpful hint?

Re: licensing backstage does not show external extension

Anonymous User — Mon, 01 Oct 2018 18:34:50 GMT

Hello Roman,

The Licensing sample should work fine for you given a Pro 2.2.2 installation. If you have had success compiling and running other samples, then as long as the Licensing sample add-in is in a well-known folder, you should indeed see the "External Extensions" entry appear on the Licensing tab. Perhaps check the add-in manager to ensure the add-in is showing as installed. If not, you might also double-check the Config.daml to ensure you have set the add-in's desktopVersion="2.0.0". If you have an older set of 1.x samples installed, these would by default not have the newer value set and would not load in a Pro 2.x installation.

Re: licensing backstage does not show external extension

RomanTrojan — Tue, 02 Oct 2018 14:14:06 GMT

Thank you, Christopher, very much!
The mess was caused by another external extension with configured <extensionConfig ... hasExtendedInfo="true"/> entry, but without correct IExtensionConfig implementation. Such DLL positioned in a well-known or optional AddIn folder supposedly obstructs license configuration for all other properly installed external extensions like Licensing sample. The desktopVersion setting or hasExtendedInfo flag set to "false" work as expected (impacting particular extension).