A project package is a package that lets you develop Creatio functionality as a standard C# project.
Project package major features
- Project packages take much faster to compile than simple packages if both contain a large number of Source code type schemas: 1-2 seconds as opposed to 30-120 seconds.
- Project packages let you deploy functionality to a production environment indirectly.
- Project packages streamline C# development for Creatio in the cloud.
- Project packages let you track the implementation dependencies. Use this to create a list of classes to test after functionality updates.
- Project packages streamline the automatic functionality tests.
Project package structure
The project package structure in the file system is identical to the structure of a simple package. The main difference between the project package and a simple package is in the Package.sln and Package.csproj files unique to the project package. Learn more about the simple package structure: Packages basics.
View the structure of project package directories in the figure below. Include the functionality developed in the project package in the package file content (the Files directory) as the compiled library and *.cs files.
Project package development tools
Creatio command-line interface utility (clio) is an open source utility for integration, development, and CI/CD.
Use the utility:
- to create a project package
- to import the package into Creatio on-site or in the cloud
- to export the package from Creatio on-site or in the cloud
- to restart Creatio
- to convert existing packages
- CreatioSDK is a NuGet package that provides a set of development tools. Use the NuGet package to create an application on the Creatio platform.
Import a project package
Compile the project package.
Compile the project package into a library as an individual C# project. The library name must match the package name. Place the compiled files to the ../Files/Bin/[PackageName].dll directory.
- Transfer the library.
- Copy the library to the directory.
- Run Creatio.
As a result, Creatio will check for qualifying libraries in the packages upon start or restart. If such libraries exist, Creatio will connect them immediately. You do not have to compile the configuration to deploy the functionality.
View the package import procedure in the figure below.