After Excel introduced the dynamic array support, files produced with the older Excel versions have formulas that may be displayed with @ in some contexts. For example a file that had the following:

=SUM(IF(A1:A10=1, B1:B10, 0))

Will be displayed like so:

=SUM(IF(@A1:A10=1, B1:B10, 0))

This is done in order to preserve the behavior of the files created in older versions of Excel.

The files created by SpreadProcessing are also treated by Excel as if they are created by pre-dynamic array Excel. Please, introduce support for the new behavior.

Workaround: this is the missing part after the export:

MS Excel offers the following text styling options:

When importing a document containing a Plain Text SDT with multiple paragraphs an exception is thrown:

Telerik.Windows.Documents.Flow.Model.Annotations.StructuredDocumentTags.Builders.SdtBuilderFailureException: "This content control type cannot be inserted around multiple paragraphs."

If a worksheet has page breaks, but Fit to pages is also set to true, the page breaks should not be respected.

wb.ActiveWorksheet.WorksheetPageSetup.PageBreaks.Clear();

An exception is thrown when the file contains the following format string 

"      PE @ "??0.0;-"      PE @ "??0.0;"      PE @   New";"      PE @ "_0_0@

The exception is thrown in the ValidateNumberFormatDescriptors method.

In excel, if you set word wrap to cell content, make the column wider and then autofit the column in which it is, the content will fit to a reasonable width, as seen in the image below.

When doing the same in SpreadProcessing, the result is always a narrow column:

            CellSelection cellSelection = sheet.Cells[0, 0];
            cellSelection.SetIsWrapped(true);

            ColumnSelection columnSelection = sheet.Columns[0];
            columnSelection.SetWidth(new ColumnWidth(100, true));
            columnSelection.AutoFitWidth();

Result:

Here are the same steps performed in WPF RadSpreadsheet, which uses RadSpreadProcessing for its engine:

Getting these Visual Studio warnings in using current Telerik.Maui and Telerik.Blazor in Build:

Detected package version outside of dependency constraint: Telerik.Documents.Spreadsheet.FormatProviders.Xls 2023.1.307 requires Telerik.Zip (= 2023.1.307) but version Telerik.Zip 2023.1.410 was resolved.

Detected package version outside of dependency constraint: Telerik.Documents.Spreadsheet.FormatProviders.OpenXml 2023.1.307 requires Telerik.Zip (= 2023.1.307) but version Telerik.Zip 2023.1.410 was resolved.

Detected package version outside of dependency constraint: Telerik.Documents.Flow.FormatProviders.Doc 2023.1.307 requires Telerik.Zip (= 2023.1.307) but version Telerik.Zip 2023.1.410 was resolved.

Detected package version outside of dependency constraint: Telerik.Documents.Fixed.FormatProviders.Image.Skia 2023.1.307 requires Telerik.Zip (= 2023.1.307) but version Telerik.Zip 2023.1.410 was resolved.

Detected package version outside of dependency constraint: Telerik.Documents.Fixed 2023.1.307 requires Telerik.Zip (= 2023.1.307) but version Telerik.Zip 2023.1.410 was resolved.

Detected package version outside of dependency constraint: Telerik.Documents.Core 2023.1.307 requires Telerik.Zip (= 2023.1.307) but version Telerik.Zip 2023.1.410 was resolved.

Detected package version outside of dependency constraint: Telerik.Documents.CMapUtils 2023.1.307 requires Telerik.Zip (= 2023.1.307) but version Telerik.Zip 2023.1.410 was resolved.

Please be sure similar warnings will not be generated in your upcoming June releases.

Thank you.


The project file references ONLY the two very latest Telerik Maui and Blazor Nuget packages, no other Telerik dlls, etc. It would seem the outdated references are internal to at least one of those nuget packages you furnish. I do not see that I have any means on my end to resolve them.