cfe-init

You can scaffold a 1C Configuration Extension by specifying the extension name and output directory. The tool automatically generates Configuration.xml, Languages/Русский.xml, and optional Roles/ structures, eliminating the need to manually write XML files.

Yes, you can auto-detect compatibility and language from a base 1C configuration by providing its file path via the -ConfigPath parameter. This allows the scaffolded extension to inherit settings without manual configuration.

Patch, Customization, and AddOn are three supported assignment variants for 1C Configuration Extensions. They categorize the extension's purpose: fixing base configuration issues, modifying existing behavior, or adding entirely new features.

You validate a generated 1C Configuration Extension artifact using the cfe-validate command. After the scaffold is created in your output directory, run cfe-validate to ensure the Configuration.xml and associated structures are correct.

Available parameters include -Name, -OutputDir, -NamePrefix, -Vendor, -Version, and -CompatibilityMode. These control the extension identity, output location, naming conventions, and versioning of the generated Configuration.xml scaffold.

Yes, the 1C Configuration Extension scaffold supports role definitions by generating a Roles/ directory. This inclusion is optional and can be controlled during scaffolding to add necessary role permissions alongside the Configuration.xml.