Usage
/epf-build <ProcessorName> [SrcDir] [OutDir]
| Parameter | Required | Default | Description |
|---|---|---|---|
| ProcessorName | yes | — | Processing name (root XML name) |
| SrcDir | no | src |
Source directory |
| OutDir | no | build |
Output directory |
Connection parameters (optional)
Preferably use a specific database: the build is more reliable, and configSrc databases from
.v8-project.json gives the source check the configuration's common modules.
- Read
.v8-project.jsonfrom the project root and resolve the database: - If the user specified connection parameters (path, server) — use them directly
- If a database was specified by name — search by id / alias / name in
.v8-project.json - If not specified — match the current Git branch with
databases[].branches - If the branch did not match — use
default - If
.v8-project.jsonis absent or the database is not found — do not specify connection parameters: the script will automatically create a temporary database. For EPF with reference types (CatalogRef, DocumentRef, etc.), metadata stubs are generated. The temporary database is deleted after the build.
Platform — v8path of the found database entry, otherwise the root v8path. Not set in either place — -V8Path do not pass.
If the used database is not registered — after execution, suggest adding it via /db-list add.
Command
powershell.exe -NoProfile -File "${CLAUDE_SKILL_DIR}/scripts/epf-build.ps1" <параметры>
Script parameters
| Parameter | Required | Description |
|---|---|---|
-V8Path <путь> |
no | Platform bin directory, or full path to 1cv8.exe / ibcmd.exe |
-InfoBasePath <путь> |
* | File database |
-InfoBaseServer <сервер> |
* | 1C server (for a server database) |
-InfoBaseRef <имя> |
* | Database name on the server |
-UserName <имя> |
no | User name |
-Password <пароль> |
no | Password |
-SourceFile <путь> |
yes | Path to the root XML source file |
-OutputFile <путь> |
yes | Path to the output EPF/ERF file |
-Checks <список> |
no | What to check before building: modules, handlers, unreferenced, empty-handlers, config; off — do not check. By default modules,handlers |
-Context <список> |
no | Check contexts modules: ThinClient, Server, ExternalConnection, ThickClientOrdinaryApplication. By default ThinClient,Server |
-ConfigSrc <путь> |
no | Directory of the XML export of the configuration in which the processing will run. By default — configSrc of the specified database from .v8-project.json |
-AdditionalV8Arguments <список> |
no | Additional launch arguments 1cv8.exe separated by commas, e.g. /UseHwLicenses+ |
-AdditionalIbcmdArguments <список> |
no | Additional arguments ibcmd separated by commas, in the form --ключ=значение |
*— optional. If not specified — a temporary database with metadata stubs is created automatically
Check before building
Before building, the platform checks the sources: module syntax and the presence of form handlers.
If there are errors, the file is not created, and the output contains the platform message with the line and column
and the path to the source file. Build without checking — -Checks off.
If the code accesses the configuration's common modules (ОбщегоНазначения, УправлениеПечатью etc.),
the check needs an export of this configuration. By default, configSrc of the specified database from
.v8-project.jsonis taken; if it is absent — pass the export directory in -ConfigSrc, and if there is no export
at all — build with -Checks off. Code that calls methods of global common modules without
a module name will not pass the check even with the export — build it with -Checks off.
Examples
# Сборка обработки (файловая база)
powershell.exe -NoProfile -File "${CLAUDE_SKILL_DIR}/scripts/epf-build.ps1" -InfoBasePath "C:\Bases\MyDB" -SourceFile "src/МояОбработка.xml" -OutputFile "build/МояОбработка.epf"
# Серверная база
powershell.exe -NoProfile -File "${CLAUDE_SKILL_DIR}/scripts/epf-build.ps1" -InfoBaseServer "srv01" -InfoBaseRef "MyDB" -UserName "Admin" -Password "secret" -SourceFile "src/МояОбработка.xml" -OutputFile "build/МояОбработка.epf"