Problems with Telerik.Licensing.Runtime

[Martin]

I'm having a repo with multiple projects which are using Telerik components. All of them are NET9/WPF/Windows currently

All projects are merged in one large solution (Master Sln), additionally we are using solution filters which are dependent on the Master Sln

The license file for each user is placed next to the Master Sln.

Now there are

• App1 which is using Telerik.Windows.Controls.Ribbon.For.Wpf.Xaml
• App2 using Telerik.Windows..Controls.Data.For.Wpf.Xaml and Telerik.Windows.Controls.GridView.For.Wpf.Xaml and a few more.

In

• App1 there is no Telerik.Licensing.Runtime copied int the output folder
• App2 has a Telerik.Licensing.Runtime in the output folder

But

• App1 works
• App2 does not work, shows the "Not Licensed" dialog and renders the "Not Licensed" pattern over the application, the reason is said to be a missing Telerik.Licensing. nuget package.

 

My question is why do I need the Telerik.Licensing.Runtime at all, since it is a compile time assembly? Additionally, all nuget packages contain Telerik.Licensing as referenced transisitive assembly.

What could be the problem why it works  with App1 and not with App2.

 

 

 

[Lance | Senior Manager Technical Support]

Hi Martin,

Thank you for the details. You've opened this post in the WinForms forums, but my answer would be the same for WPF or WinForms.

Okay, let me get right to the point... the entrance assembly is ultimately the one that needs to invoke the license check in this scenario. This prevents unauthorized/unlicensed use of the Telerik assemblies after you've shipped your product.

So, if you have access to the start up project, just install Telerik.Licensing NuGet package into the startup project (even though it doesn't use any Telerik components) and we'll do the validation at build time. Please see the instructions here and choose one of the two approaches:

• License Key Invalid When Telerik is Installed in a Controls Class Library Referenced in the Main Project

Tip: I recommend this approach for you, since it seems you are using NuGet packages for the projects.

However, if that doesn't work or cannot be applied in your situation (i.e. DLLs only), then you can attempt the "Add In" approach. Please see the following KB article instead:

• Telerik License Key Invalid or Missing Message Box and Watermark Displayed in a Excel VSTO Add-in/Plugin Project

Tip: If you use Telerik.Licensing.Runtime v1.6.7 (or later), then you can call that TelerikLicensing.Register() method without the key value.

 

Further Assistance

If you have any trouble implementing these, please open a support ticket so that you can work directly with the Telerik UI for WPF engineers.

1. Go to our Technical support portal => https://www.telerik.com/account/support-center/contact-us/ 
2. Select "Technical support" (not Licensing Support)
3. Next, select "UI for WPF" and then "General" for the topic.
4. In the body of the message you can put a link to this forum post for some initial information, but also please explain further on why it didn't work.
   • Note: It is a private and protected conversation, you can share more specific details safely in there... whereas in this public forum you could not.

I hope this information helps get you up and running again.

Regards,
Lance | Senior Manager Technical Support
Progress Telerik

[Martin]

Hi Lance, thanks for the tips.

What puzzles me a bit is that both apps App1 and App2 do not have a nuget reference to Telerik.Licensing, and App1 works, but not App2. None of them have a direct reference to Telerik.Licensing. I'm not sure how its done, but as far as I can see the Telerik.Licensing adds an msbuild target where I assume the licenses are checked.

As a side not: App1, which works, has no Telerik.Licensing.Runtime in the out directory, whereas App2 has it, but does not work.

Since Telerik.License is a transitive assembly of some other Telerik component, it seems there is the transitive msbuild dependency missing which would work if the target in the nuget package is also added to buildTransitive in the nuget package.

I consider the addition of Telerik.Licensing as a workaround for the missing transitivity of the package, because many analyzers would tell me that the package is not required since it is already contained in a direct package.

 

Does this make sense?

 

 

[Lance | Senior Manager Technical Support]

Hi Martin,

Thank you for the additional context, yes, it does make sense. It comes down to the project type and whether or not they can execute a build task that resides in the Telerik.Licensing NuGet package.

For 99% of the situations, there is no runtime activation, it happens at build time. We use the build task to automatically generate an EvidenceAttribute that is then checked at runtime. However, in some project types that cannot use that build task (such as old school .NET Framework types without PackageReference), there needs to be some extra effort at runtime, which requires the Telerik.Licensing.Runtime assembly and a call to TelerikLicensing.Register().

I see you have opened a support case, thank you. I have escalated it to the correct team, they can provide some more inner operational details to explain the behavior in your situation, and how to solve the issue for the project that cannot use out build-time evidence.

[Martin]

@Lance. Thanks a lot for forwarding it. Unfortunately once the ticket is opened I cannot edit it anymore.

[Lance | Senior Manager Technical Support]

Just post an additional reply, no need to edit any existing items.

I'm closely watching it and I have already escalated it. Though please note that the team is located in Sofia, BG. So, unless someone is doing an unusual weekend shift, you probably wont get an answer until Monday morning (~2-4am ET).