The new license key, how does it work with the build machine?

1 Answer 119 Views
Licensing
BENN
Top achievements
Rank 1
BENN asked on 17 Feb 2025, 07:22 AM | edited on 17 Feb 2025, 07:26 AM

Do I need to put the license key on the build machine, or only on the dev machine? (As I understand, an invalid license would cause a compile errors / warnings during build, and also watermarks when application starts, so I'm guessing that the build machine needs a license).

 

I see that the license can either be in %appdata% or in the root folder of the project, or embedded in the project as TerlerikLicense.cs with:

[assembly: global::Telerik.Licensing.EvidenceAttribute

 

You also write: "Do not commit the file to source control as this is your personal license key"

So how does it work with adding you TelerikLicense.cs to the project? Wouldn't adding it to the project is like adding it to git? (since entire project is committed)

 

Thanks

1 Answer, 1 is accepted

Sort by
0
Accepted
Martin Ivanov
Telerik team
answered on 17 Feb 2025, 08:50 AM

Hello Benn,

The recommended approach to store the license key on a build machine is to use an environment variable. This is mentioned in the following article. I hope that helps.

Regards,
Martin Ivanov
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

BENN
Top achievements
Rank 1
commented on 17 Feb 2025, 01:17 PM

OK, thank you.
BENN
Top achievements
Rank 1
commented on 18 Feb 2025, 02:58 PM | edited

Hi Martin, just few more question:

According to: https://docs.telerik.com/devtools/wpf/getting-started/licensing/license-activation-errors-and-warnings the license can expire / not be valid for several reasons.

1) Assuming I have a license up until mid 2026. Would I be still be able to build versions using 2025 dlls (in case the subscription is not renewed)?

 

2) Is the new license (after renewing on 2026) can be used when building with dlls from 2025? (for example, I need to rebuild an old version for a Service Pack)

 

Thanks

Martin Ivanov
Telerik team
commented on 21 Feb 2025, 01:16 PM

(1) It depends on the license type - perpetual or subscription. With perpetual, you will be able to use the 2025 versions regardless of the current date. With subscription, the product can be used only during the subscription period. After that you will see warnings and other type of banners. However, once you subscribe again, you can use the 2025 versions properly again.

Read more about the licenses on the telerik.com website.

(2) Yes, the new license can be used for older versions.

Tags
Licensing
Asked by
BENN
Top achievements
Rank 1
Answers by
Martin Ivanov
Telerik team
Share this question
or