Reporting Visual Studio Extension Export License Watermark

[Benedikt]

Hi,

I have the Visual Studio Reporting Extension Installed on my machine.

If I export a pdf from a report with it, i get the license watermark everywhere.
But I have a license and the License Extension tells me its downloaded.

Is this right?
Or is something missing/corrup with my extension?

 

Greetings
Benedikt

[Nicholas]

You have to reference the Telerik.Licensing NuGet package in each of your startup assembl(ies) (web app, console app, etc,), even if your Telerik reporting stuff is in a separate DLL that your startup assembl(ies) reference.

For example, if you have FooBar.WebApp that references a project FooBar.Reports that contains all your reports and code to generate PDFs from them by referencing Telerik.Reporting, you also need FooBar.WebApp to reference the Telerik.Licensing even if it doesn't directly use Telerik.Reporting.

Or...you can add a class like this to FooBar.Reporting and just invoke LoadLicense (perhaps in a static constructor)  before using the Telerik stuff. (My extension methods should be self-explanatory)

using System;
using System.Linq;
using System.Reflection;
using Telerik.Licensing;

namespace FooBar.Reports;

public static class TelerikLicenseHelper
{
 private static bool __licenseLoaded;

    internal static void LoadLicense(bool validate = true)
 {
        if (__licenseLoaded)
            return;

 var assembly = typeof(TelerikLicenseHelper).Assembly;
 assembly.GetCustomAttributes<EvidenceAttribute>()
            .Select(a => a.Value)
            .NotNullOrWhiteSpace()
            .ThrowIf(vs => !vs.Any(), _ => new ApplicationException( $"Cannot find {nameof(EvidenceAttribute)} with populated license key in {assembly}"))
 .ForEach(s => TelerikLicensing.Register(s));

        if (validate)
{
 var license = TelerikLicensing.License<Telerik.Reporting.Report>();
            if (license?.IsLicenseValid != true)
 throw new ApplicationException(license?.RuntimeConsoleMessage() ?? "[license is null]");
 }        
        __licenseLoaded = true;
    }
}

 

[Benedikt]

Hi Nicholas,

I think I know what you mean, but I also think its not quite my problem.

I have a project with just one assembly.
And this has the Nuget package referenced.
Also from code the report works just fine and exports also without watermark.

It is just from the Visual Studio extension preview that it exports with watermark.

What it didnt do before the new licensing system.

With your code snippet, it wont start the preview now. I get this error, but I don't know what license that should be thats missing.
I mean I have Reporting. And from code it works, so doesn't this mean I have all the licenses I need?

[Petar]

Hello Benedikt,

If I understand correctly, the watermarks appear when exporting the report directly from the "Preview" mode of the Visual Studio Report Designer, correct?

If that is the case, it is possible that the licensing assembly may not be recognized by the designer. I recommend copying the `Telerik.Licensing.Runtime.dll` assembly from the `bin` directory of the application that builds correctly (and does not display any watermarks) and placing it in the directory that contains the `devenv.exe.config` file for Visual Studio. By default, this file should be located at:

• C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE

Then, try reopening Visual Studio so that the licensing assembly can be taken into account.

Could you please try this approach and let me know if it works for you?

If you believe I misunderstood your scenario, I would appreciate it if you could provide any additional details, and I will do my best to assist you further.

Regards,
Petar
Progress Telerik

[Benedikt]

Hi Petar,

you got it completely right.

I did try this approach but the watermark still appears sadly.

 

Greetings,

Benedikt

[Petar]

Hi Benedikt,

Thank you for the confirmation.

This observed behavior looks odd.

Could you please attach a trace listener to the Visual Studio Report Designer and provide the generated log file for further investigation? For guidance on how to create this log file, you can refer to the article Troubleshooting Visual Studio Report Designer. After attaching the trace listener, make sure to reproduce the issue locally so that the necessary information can be stored within the log.

Looking forward to your reply!

Regards,
Petar
Progress Telerik