Error occurred when loading .xls file using GroupDocs.Metadata.Formats.Document.XlsFormat

GroupDocs.Metadata Product Family
1

Hi Aspose team,

We use v19.4 lib and find a problem. When loading a .xls file using XlsFormat class, it throw an exception(Invalid xls format).

code : var format = new XlsFormat(filePath);
file:OF2013_Book1.zip (2.9 KB)

2

@Glority_Developer,

We are able to reproduce your reported issue at our end. The issue has been logged into our Issue Tracking System as METADATANET-2909 for further investigation. We shall notify you as soon as we have any updates for you.

3

@Glority_Developer,

Our investigation revealed that the exception occurs because the problematic Excel file is not actually an Excel 97-2003 workbook. It has been saved in the Microsoft Excel 5.0/95 format which is not currently supported by GroupDocs.Metadata. Both these formats have the same extension - XLS, so it’s easy to mix them up.

To resolve this issue, we have added the support of Excel 95 workbooks to GroupDocs.Metadata and this feature will be available from version 19.6. We shall notify you here as soon as the v19.6 is released.

4

@Glority_Developer,

Unfortunately, the release of GroupDocs.Metadata for .NET 19.6 has been postponed. However, we have included the bug fix for your reported issue (logged as METADATANET-2909) in GroupDocs.Metadata for .NET 19.5.1 hotfix. Using this version, you will be able to load the Microsoft Excel 5.0/95 format, however, the API will automatically update the format to the Excel 97-2003 once you will save the document.

5

Thanks for your reply.

Can you tell us specific time of the GroupDocs.Metadata for .NET 19.6 release? We plan to update this dll in our code at the end of June.

Also, if 19.6 is released, the behavior of this issue will still be the same as the v19.5.1 dll? If so, we would use this v19.5.1 dll unless 19.6 can be released within our expected time.

6

@Glority_Developer,

Unfortunately, v19.6 would not be released in June and at the moment, we can not share the ETA with you. However, as soon as we have any further updates, we shall share that with you.

Yes, the fix that we have provided in v19.5.1 will also be the part of v19.6. Furthermore, the behavior of the API for this issue will also be the same in both versions.