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 telerik.com, 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.

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.

Hi there I have a pdf and whenever I try to Import the PDF file into PdfFormatProvider.Import method for flattening purposes, it throws null reference exception.

I have added a sample .net project with PDF added as source. You just need to run the project on your end. I am using version 2023.3.1106 of document processing library.

I am using ASP.NET 4.8 framework.

Thanks

Forecolor of table cells text is not preserved when exporting to PDF

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.

Exception when using multiple instances of RtfFormatProvider

Exception when converting to PDF and there are cells with a width less then 5.

Exporting documents with PrintTitles and sheet names containing spaces causes missing PrintTitles.

When exporting a rotated page from a PDF document to an image, the resulting image is the wrong size, and the page looks clipped.

InvalidCastException 'Unable to cast object of type 'EffectContainerElement' to type 'EffectListElement' is thrown on import.

As a workaround, you can either use the old version of the assemblies (R2 2022) or you can set ImportSettings.SkipShapes of the DocxFormatProvider to true.

The NotBetween conditional formatting rule applies the format to all the cells, no matter if the rule is satisfied or not.

The print title defined name can contain any type of formula or literal and the document will still be valid. However, SpreadProcessing expects a cell range reference and throws and exception if the name contains something different.

When a workbook contains two charts (regardless of whether they are in the same sheet or not) and both of them contain axes, the resulting document will be invalid and Excel will not be able to open it.

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.

The auto row height is not working when the row is merged. This is only valid if the merged cell range contains a single row.

Importing an XLS document containing header/footer definition without a specific placement causes an endless loop. 

Importing an XLS file containing many merged cells is slow.

NullReference exception is thrown when importing document with docx AltChunk element.

Charts containing marker definition, even its symbol and fill properties are set to none are drawn.