Kentico Xperience 13 documentation and ASP.NET Core

Most documentation about running Xperience applications under ASP.NET Core can be found in a dedicated section: Developing Xperience applications using ASP.NET Core. The rest of the documentation still applies, but some code samples and scenarios might need slight modifications for Core projects.

All major differences between the MVC 5 and Core platforms are summarized in Migrating to ASP.NET Core.


Developing custom translation services

In addition to the translation providers available by default, you can also integrate any other services or your own translation mechanisms.

To add a custom service:

  1. Create a class that defines the translation functionality or the communication logic between Xperience and an external service. The implementation rules for the class are different for machine and human translation services. You can find detailed information and custom development examples for the two types of services on the dedicated pages:
  2. Add a new assembly (Class Library project) to your Xperience solution and include the service class there. You need to add the appropriate references to both the assembly and the administration project.
  3. Register the service in the system via the Translation services application and specify its properties.
  4. Create Custom settings for any additional parameters required by the service, such as connection credentials or API keys.
    • The settings allow administrators to configure the service for specific websites or translation projects.

When translating pages or resource strings, users can choose custom services among the translation options offered by the system.

Enterprise license required

Features described on this page require the Kentico Xperience Enterprise license.

Was this page helpful?