Skip to content

Dess trial dev #1665

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Dess trial dev #1665

wants to merge 4 commits into from

Conversation

dessyordanova
Copy link
Collaborator

No description provided.

@dessyordanova
Copy link
Collaborator Author

This should be reviewed and merged for the Q2 2025 release.

@dessyordanova dessyordanova self-assigned this Apr 16, 2025
@@ -11,7 +11,9 @@ previous_url: /installation-trial-license-limitation

# Telerik Reporting Licensing before 2025

Telerik Reporting comes in trial and developer (or commercial) licenses.
Telerik Reporting used to come in separate **Trial** and **Developer** (or commercial) assets distribution until **Q2 2025**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Telerik Reporting used to come in separate **Trial** and **Developer** (or commercial) assets distribution until **Q2 2025**.
Before Q2 2025, Telerik Reporting was distributed in two versions: Trial and Developer (commercial), each having its own assets. Starting with Q2 2025, Telerik Reporting comes in a unified installation package regardless of whether you have a developer (commercial) or a trial license.

Telerik Reporting comes in trial and developer (or commercial) licenses.
Telerik Reporting used to come in separate **Trial** and **Developer** (or commercial) assets distribution until **Q2 2025**.

>caution After launching the [new licensing mechanism in Q1 2025](https://www.telerik.com/blogs/license-key-files-telerik-kendo-ui-products-2025-update), the activation is performed through a [license key]({%slug setting-up-license-key%}) (trial or commercial). Upgrading from a Trial to Developer (or commercial) version requires only updating the license key without the necessity of reinstalling the respective Telerik product.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
>caution After launching the [new licensing mechanism in Q1 2025](https://www.telerik.com/blogs/license-key-files-telerik-kendo-ui-products-2025-update), the activation is performed through a [license key]({%slug setting-up-license-key%}) (trial or commercial). Upgrading from a Trial to Developer (or commercial) version requires only updating the license key without the necessity of reinstalling the respective Telerik product.
>caution Starting with [Telerik Reporting version Q1 2025](https://www.telerik.com/blogs/license-key-files-telerik-kendo-ui-products-2025-update), you must activate the product through a [license key]({%slug setting-up-license-key%}) (trial or commercial). To upgrade from a Trial to a Developer (or commercial) license, purchase a license and then download a new license key, without re-installing the product.


## Description

This tutorial explains in detail how to upgrade your Telerik [Trial]({%slug telerikreporting/licensing%}) to a Licensed version of [Telerik Reporting](https://www.telerik.com/account/product-download?product=REPORTING).

>caution This approach is valid for versions [before Q2 2025]({%slug telerikreporting/licensing%}). After launching the [new licensing mechanism](https://www.telerik.com/blogs/license-key-files-telerik-kendo-ui-products-2025-update), the activation is performed through a [license key]({%slug setting-up-license-key%}) (trial or commercial). Upgrading from a Trial to Developer (or commercial) version requires only updating the license key without the necessity of reinstalling the respective Telerik product.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See the previous suggestion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants