cfe-init

To scaffold a 1C configuration extension XML structure, you generate Configuration.xml and Languages/Русский.xml files along with optional Roles directories. This creates a minimal valid extension skeleton to start development immediately without manually assembling XML.

Yes, you can auto-resolve CompatibilityMode and Language UUID from a base 1C configuration export. By providing the ConfigPath parameter pointing to the base configuration files, the scaffolding process reads and applies these settings automatically to the new extension.

Patch, Customization, and AddOn are Purpose parameters that define the extension type during 1C configuration extension creation. Selecting the appropriate purpose ensures the generated Configuration.xml conforms to the correct structural requirements for the specific extension modification type.

To generate a 1C configuration extension without a main role, use the NoRole option during the scaffolding process. This omits the Roles directory from the generated XML structure, suiting extension scenarios that do not require role-based access definitions.

1C configuration extension scaffolding fails if Configuration.xml already exists to validate idempotency and prevent overwriting existing work. This safety mechanism ensures that the deterministic XML generation process does not corrupt or duplicate an established extension structure.

Yes, you need PowerShell to run the script that generates 1C configuration extension XML files. The scaffolding tool executes via powershell.exe using parameters like Name, ConfigPath, and OutputDir to deterministically produce the required Configuration.xml and language files.