In Development
Last Updated: 14 Oct 2019 14:42 by ADMIN
Created by: Tanya
Comments: 75
Category: Telerik Document Processing
Type: Feature Request

Currently, Telerik Document Processing is available only for .NET Framework and (partially) for Silverlight. Create version targeting .NET Core.

Update: There is a version of Telerik Document Processing compatible with .NET Core 3.0 in the UI for WPF suite. You can use this version in .NET Core projects running on Windows. The assemblies can be downloaded from, the Downloads section of UI for WPF -> Betas tab. Please, note that you should have a valid license for UI for WPF in order to be able to see this version. In case you don't, you can use the Trial license by downloading a trial version of the suite. More information about this version of UI for WPF and how it can be used is available in the related blog post.
Last Updated: 25 Sep 2019 15:57 by ADMIN

The NuGet packages don't differ .Net Core projects from .Net Core with Desktop Compatibility Pack. This leads to incorrect resolving of the dependencies and the .Net Core projects targeting .Net Core 3.0 cannot be built.

Workaround: An option applicable for all the libraries is to extract the assemblies from the .nupkg files. For PdfProcessing and ZipLibrary you can use the assemblies directly from the pdfviewer installation folder.

Last Updated: 15 May 2019 14:18 by ADMIN
Created by: Hector
Comments: 1
Category: Telerik Document Processing
Type: Bug Report
Testing Tracked Forum
Last Updated: 12 Apr 2019 14:45 by ADMIN
Created by: David
Comments: 7
Category: Telerik Document Processing
Type: Feature Request

I'm working on a project that has a service component that will be generating Excel xlsx documents for distribution.  While there is a UI for administrative tasks, the service itself will run without an interface.  I'm using the Documents.Core, and several other associated libraries to accomplish this.  Two issues I've encountered, one is setting up the project with the appropriate libraries and keeping the version in sync with the Admin application, second is protecting those libraries once they are packaged for release.  I had a support ticket open to determine how to accomplish the latter, but the first is still a manual issue.  

So the feature request is to include the ability in the project templates and/or Convert to Telerik WPF Application to support a headless document solution.  It would ideally include (only) the required libraries and maintain their linkage to the appropriate library version with the rest of the solution which occurs with a full Telerik WPF UI app.  It would also include the necessary boilerplate code and references to properly protect the libraries.  I was referred to another feedback request on improving the overall library protection build process, but while related, what I'm asking for here is not exactly the same.

Last Updated: 25 Jan 2019 14:50 by ADMIN
Encrypting document with Interactive forms containing checkboxes exports the checkbox widget with invalid normal caption appearance and name value. After the document is visualized in Adobe Reader DC the exported checkboxes are displayed with different check mark symbol or none.
Last Updated: 17 Dec 2018 13:42 by ADMIN
Created by: Stefan
Comments: 1
Category: Telerik Document Processing
Type: Bug Report
When two documents are merged and the source document has watermarks, these are not cloned in the target document.

Last Updated: 12 Nov 2018 18:41 by ADMIN
When using the PdfStreamWriter to write a PdfPageSource whose content is an array of content streams, the resultant content stream contains concatenated graphic state operators. This results in error when loading the document in Acrobat Reader and corrupted page content.
Last Updated: 12 Nov 2018 15:45 by ADMIN
When there is an abstractNum defined with the same abstractNumId in word\glossary\numbering.xml and in the word\numbering.xml, a "System.ArgumentException: An item with the same key has already been added." exception is thrown.

In other cases, the import overwrites the styles from the main document part with the ones defined in the glossary. 

Last Updated: 12 Oct 2018 22:26 by ADMIN
When xlsx/docx document is imported, and its main story is with non-default name ('workbook. xml'/'document.xml'), e.g. workbook2.xml/document2.xml, NullReferenceException is thrown and the document is not imported.

Note: Such documents are usually produced after conversion from a template dotx/xlsm.
Last Updated: 05 Apr 2018 11:52 by ADMIN
Currently EULA requires Telerik assemblies to be protected against unauthorized redistribution, by following specific guidelines for the different types of technology:
- for WPF:
- for WinForms:

When the guidelines for WinForms or AJAX are followed (namely the call to ValidatePassPhrase() is uncommented in AssemblyProtection.IsValid() method, the following license message is added to the generated documents:
"This document was generated by a copy of Telerik Document Processing licensed for use only by '<MyApp>'."

Workaround: Set the application name as resource in the Application.Current, using the following code:

new System.Windows.Application();
System.Windows.Application.Current.Resources.Add("Telerik.Windows.Controls.Key", "MyApp");
where 'MyApp' should be replaced with the actual application name. References to PresentationFramework and WindowsBase .NET Framework assemblies should be added in order for this approach to work.