Creatio on the .NET Core platform
Taking the growing demand for open-source software that can be deployed on Linux-based OS, Creatio has implemented support of the .NET Core platform.
Advantages of products that are based on .NET Core
In addition to being open-source, .NET Core is a cross-platform solution that can support deployment on Linux, Windows, and Mac OS.
We recommend using a Linux OS for Creatio deployment: this operating system offers high reliability and performance and is being actively developed.
Application features on .NET Framework and .NET Core platforms:
|
.NET Framework functionality |
Current .NET Core implementation |
Plans for .NET Core support |
|---|---|---|
|
LDAP integration |
A separate .NET Core instance is used for the synchronization of Windows-based applications. |
Linux support is planned after the implementation of corresponding functionality on .NET 5. |
|
Phone integration |
Cisco, Avaya, TAPI, and Infinity integrations require the allocation of the messaging service on Windows. To integrate with Cisco Finesse, deploy the Microsoft IIS web server and its extension - Application Request Routing (ARR) on Windows. |
Future releases will support messaging service of all phone integrations, except for TAPI, since it is Windows-exclusive. Future releases will be able to integrate with Cisco Finesse without using IIS and ARR. |
|
Setting up MS Word report templates |
Creatio MS Word plugin (required to set up a template) must connect to a .NET Framework Creatio application. The configured template can be used in a .NET Core application. |
Supported, starting with 7.16.2. |
|
Oracle DBMS |
Not supported currently. |
Will be supported in future releases. |
|
Fault-tolerant Redis Sentinel configuration |
Not supported currently. |
Redis Sentinel support is not currently planned. Future releases will support a more modern Redis Cluster instead. |
|
Exchange/Office365 calendar and contact synchronization |
Not supported currently. |
Will be supported in future releases. |
|
Google contacts and calendar synchronization |
Not supported currently. |
Will be supported in future releases. |
|
Facebook integration |
Not supported currently. |
Will be supported in future releases. |
|
.NET Framework functionality |
Supported, starting with version |
|---|---|
|
Windows authentication |
7.16.4. |
|
Configuration development (the [Configuration] section, Object Designer) |
7.17.0. |
Application life cycle on .NET Framework and .NET Core platforms
Microsoft plans to merge the two platforms into a single .NET 5 platform in November of 2020.
Most of the APIs that were previously supported on .NET Framework will be supported on .NET 5 as well. It is worth noting that the API is not reverse-compatible, so supporting .NET Core in the future, .NET 5 would need to adapt functions developed on .NET Framework to .NET Core.
Creatio plans to switch all its products to the single .NET platform.
To simplify future adaptation to .NET Core and .NET 5, we recommend developing any new functions with both .NET Framework and .NET Core support.
Development and customization support for products on the .NET Core platform
Most development and customization tools already support .NET Core platform. The following low-code tools are already supported: Process Designer, Section Wizard, Detail Wizard, Mobile App Wizard.
The following command prompt utilities for development automation also support the platform: WorkspaceConsole, clio.
Support for the [Configuration] sectin is currently in development. The [Configuration] section is currently in development. Planned support for the Object Designer. Currently, these tools are available on Windows. Customizations can be applied by transferring corresponding packages on Linux.
ATTENTION
If you are using any Marketplace apps to extend the functionality, please make sure that they support .NET Core.
Development with simultaneous .NET Framework and .NET Core support
Recommendations:
1. Any external libraries used must support .NET Standard 2.0. This enables using them in .NET Framework and in .NET Core.
2. The API of any framework used must support .NET Standard 2.0. Use the following Microsoft documentation to verify the .NET Standard 2.0 conformity:
3. Designing configuration web services requires inheriting from the Terrasoft.Web.Common.BaseService class and using HttpContextAccessor to access HttpContext. Additional information is available in the "Creating a custom configuration service"
Migrating from a .NET Framework application to a .NET Core application.
Future releases will support migration from .NET Framework applications to .NET Core applications.
Deployment of Creatio applications on .NET Core
The deployment guide for Creatio products that are based on .NET Core is available in Creatio documentation.
