Resolving Trial Watermark Issues with the Generated Documents in MFC applications
Environment
| Version | Product | Author |
|---|---|---|
| 2026.1.210 | Telerik Document Processing | Desislava Yordanova |
Description
When generating documents in MFC (Microsoft Foundation Class) applications with Telerik Document Processing libraries, a trial watermark may be observed even though the license is properly setup. This issue can occur even if a valid license is detected during the build phase, as indicated by the build output.
Solution
To resolve a license issue with Telerik Document Processing in MFC applications, follow the steps:
-
Ensure that the Telerik.Licensing NuGet package is directly referenced in the startup project. For .NET Framework startup projects that do not use the SDK-style project structure, ensure that there is one or more Telerik Document Processing NuGet packages/assemblies referenced in the project. If the startup project contains no Telerik Document Processing references and is not defined as SDK-style project, and is instead referencing other projects that contain the Document Processing-related code, our licensing mechanism cannot determine that any Telerik products are used, thus the license check will be False at runtime.
-
Ensure that a valid license key is present and correctly configured.
-
Call the TelerikLicensing.Register method as early as possible in your project since there is not strict entry point.
-
Use Document Processing version that matches the corresponding Teleri.Licensing version. MFC C++ application have no binding redirect and it is possible to load different versions of Telerik.Licensing, respectively you call .Register() on one, and the libraries look for a license on another. That is why we should strictly follow the corresponding versions. For example:
-
Document Processing Version 2025.4.1319 matches Telerik.Licensing 1.6.36.
-
Document Processing Version 2026.1.210 matches Telerik.Licensing 1.6.40.
-
Document Processing Version 2026.1.304 matches Telerik.Licensing 1.7.0.
-
-
Troubleshooting Steps: Check the loaded assemblies after the code for producing the document:
Assembly entryAssembly = Assembly.GetEntryAssembly();
Debug.WriteLine(" - EntryAssembly: " + entryAssembly.FullName);
foreach (var assembly in AppDomain.CurrentDomain.GetAssemblies())
{
Debug.WriteLine(" - LoadedAssembly: " + assembly.FullName);
}