Extension Deployment

First considerations

Extension deployement should not be considered as an independent task. Indeed, when you need to deploy extensions on a number of workstations, you'll need also to deploy models, shortcuts, gallery themes, and so on, because you'll need to preserve a relative homogeneity. In fact, you'll often need de deploy extensions in the same time you need to deploy models, shortcuts and gallery themes.

That's why it is suggested here to consider the following approach: 1 - to define the structure of a package which aims to deploy in one operation extensions, includind macro and toolbars, models, shortcuts and gallery themes; 2 - to define the user interface of an administration tools whose goal is to create such a package; 3 - to define the user interface of a user tools which would enable the end user to install the package on her workstation, or the administrator in the shared installation tree.

Technical constraints

Before specifying the content of the package, we must keep in mind some technical contraints induced by the implementations of the configuration objects, and the rules for specifying their location.