About releases variants

The Open Integration Package is a project with three development paths: 1C, OneScript, and CLI. The main version is 1C, which is then automatically transformed into a package for OneScript, and from there into a CLI application. Each of these paths has its own distribution options – there are 8 in total: 3 for 1C, 4 for CLI, and 1 for OneScript. Descriptions of each of these are provided below

To the latest release: Click!

1С:Enterprise

These release options are various forms of distribution for the extension for the 1C:Enterprise platform

OpenIntegrations_x.x.x.cfe - the standard distribution option for the 1C configuration extension. To start working, it is sufficient to load it into the list of extensions for your specific configuration. Development is carried out in compatibility mode with 1C 8.3.9.

XML.zip - this is a zip archive that contains the files of the standard 1C extension export "to files". Similar to the CFE option, the unpacked archive can be used to load the extension through the Configuration Extensions panel in a specific project

EDT.zip - this is a zip archive that contains the files of the EDT extension project. This distribution option is intended for quickly starting work with the Open Integration Package in cases where the development of the main configuration is carried out using 1C Enterprise Development Tools

CLI

these release options are various forms of distribution for OInt CLI – a cross-platform terminal/command line application that implements the full functionality of the OpenIntegrations library without being tied to the 1C/OS technology stack. The system requirements for OInt are the system requirements for OneScript: .Net Framework 4.8 (Windows) or a comparable version of Mono (Linux)

oint.exe - an executable file that, despite its Windows-oriented extension, is cross-platform. It requires .Net Framework 4.8 or a compatible version of Mono to run. In Windows and Debian-based distributions, this application is launched simply through the command line/terminal, while in RHEL-based distributions, it is launched through mono oint.exe "$@"

oint_x.x.x_installer.exe - this is a Windows installer. It is the recommended installation method for Windows OS, as it automatically creates the program directory and sets the PATH (after restarting the computer). This allows the application to be launched from any location by simply typing oint in the command line

oint_x.x.x_all.deb - this is a DEB package designed for installing OInt on Debian/Ubuntu distributions. When using it, Mono dependencies are installed automatically, so no additional actions are required to start working

oint-x.x.x-1.el7.x86_64.rpm - this is an RPM package designed for installing OInt on RHEL/Fedora/CentOS distributions. When using it, Mono dependencies are installed automatically, so no additional actions are required to start working. Also, there is no need to run it through mono, as with the exe.

OneScript

These release options are intended for use in OneScript projects

oint-x.x.x.ospx - this is an OSPX package intended for installation via the OPM package manager. You can use it for offline installation using the command opm install -f "./OInt-x.x.x.ospx". But it is much easier to install OInt directly from the package hub. You don't need to download any files for this, just execute the command opm install oint