Scope: managed applications, mobile applications, and ordinary applications.
1. Prepare distribution packages for installing and updating applications or configurations of 1C:Enterprise 8 in accordance with recommendations listed in chapter 30 "Configuration delivery and support" of the Developer Guide included in documentation package for 1С:Enterprise 8 software.
<Templates directory>\<developer directory>\<configuration directory>\<version directory>
In the version directory, use underscores instead of dots.
For example, Trade Management 188.8.131.52 (version 11.1) is saved to the following directory:
3. The version directory must contain the 1cv8.mft manifest file, where installed configuration templates (.cf) and demo infobases (.dt) are described.
For example, the manifest file of Trade Management 11.1 that is installed together with 2 infobase templates: an empty infobase for further work and a demo infobase.
Catalog=1С:Trade Management/Trade Management
Catalog=1С:Trade Management/Trade Management (demo)
In the Catalog string of the manifest file, explicitly insert the developer name in the configuration template name (before the slash mark "/"). You can insert the developer name anywhere in the configuration template name, for example:
Trade Management (1С).
In the Destination string, specify the recommended directory for saving an infobase as follows:
Destination = <developer directory>\<infobase directory>.
The <developer directory> must contain the developer name, but it is to be adapted for use in file directory names.
For example: 1C\Trade.
4.2. To avoid duplicates, use globally unique names of developers supplying applications or configurations: a name to be used in configuration template description and a name to be used in file directory names.
The developer name is selected once. Further, a developer can use it upon installing or registering templates of all applications developed by them for 1C:Enterprise 8.
The basic recommended update method with the help of Designer is search for appropriate update files (menu Configuration - Support - Update configuration). Configurations might also provide other tools for updating versions. If Standard Subsystems Library is used in a configuration, such feature is available in the "Configuration update" subsystem.