Deploy Add-In's via App Config

[SeanLynch]

According to the AGX documentation (quoted below) you are supposed to be able to deploy add-in's to users via a custom application configuration file.

[INDENT]"Application customizations allow you to deploy custom add-ins throughout your organization without your end users having to configure them or even be aware that they are using add-ins. An application configuration allows you to centrally manage both the deployment and the updating of add-ins that your users need."[/INDENT]

I have created an application configuration which includes the add-in's (.eaz's) to be deployed.  However, whenever I use the app config the add-in's don't show up.  It appears that I have to explicitly go into the "Options" and use the ArcGIS Explorer Add-Ins dialogue to manually choose the add-in's.  I thought the application configuration would include them so that my field users would not have to manually add them or otherwise manage them...?

Any ideas or suggestions woud be greatly appreciated.  Using build 1200.  Thanks.

[MichaelBranscomb]

Sean,

Your interpretation of the ArcGIS Explorer documentation is correct - you can deploy custom Add-Ins (.EAZ) via Application Configurations with the configuration file (.NCFG) physically containing any Add-Ins you have added via the Application Configuration Manager, in addition to a custom map you may have chosen. This means you only need to share a single file or better perhaps, configure users ArcGIS Explorer applications to start with you chosen NCFG by default.

When adding custom Add-Ins - you'll need to make sure you add them to the actual UI (described in http://webhelp.esri.com/arcgisexplorer/1200//en/appconfig_customize_ui.htm#add_addins) by chosing "Add Custom Control...". Going through the process described in the above help document will add the custom Add-In to the NCFG AND ensure it is displayed in the intended place on the UI.

There is another dialog (described in http://webhelp.esri.com/arcgisexplorer/1200//en/appconfig_add-ins.htm) which conveniently gives a single view of all custom Add-Ins that have been added to the configuration. This is a necessary because you may have added multiple Add-Ins and directed them to multiple different tabs. Note however, that this dialog may also show Add-Ins which have been imported to the NCFG but have yet to be assigned to display on the UI.

I hope this helps

Regards

Mike