Content of XLS file is changed after loading and saving back

Aspose.Cells Product Family
1

Hi,

I’m having an issue with a file when using lastest Aspose .NET 20.10. I only load the sample file then save it back to XLS format, and the content changed to #value

My sample code:

var opt = new LoadOptions
{
MemorySetting = MemorySetting.MemoryPreference
};
var workbook = new Workbook(@“D:\sample.xls”, opt);
workbook.Save(@“D:\out.xls”, SaveFormat.Excel97To2003);

Here is sample file and output file: data.zip (17.6 KB)

I’m using the lastest version of Aspose Cell 20.10 to test this issue.

Thank you.

2

@dunghnguyen,
We have logged the issue as “CELLSNET-47675” in our database for investigations. Once we will have some news for you, we will update you in this topic.

3

@dunghnguyen,

This is to inform you that we have fixed your issue now. We will soon provide you the fixed version after performing QA and incorporating other enhancements and fixes.

4

@dunghnguyen,
You may please give a try to the following hot fix and share the feedback.

Aspose.Cells20.10.4 For .Net4.0.Zip (5.4 MB)
Aspose.Cells20.10.4 For .Net2_AuthenticodeSigned.Zip (5.4 MB)

5

Hi @ahsaniqbalsidiqui,
The hot fix resolved our problem with attached file. Thank you a lot.

6

Hi @ahsaniqbalsidiqui,
When testing the hotfix, I found that there is different from version 20.10.0 with hotfix 20.10.4. Abstract base class name “T:Aspose.Cells.CollectionBase`1” is removed in hotfix 20.10.4, which cause some issue in my project.
Here is the different in metadata xml file: AsposeCells.png (48.8 KB)

My question is: is this a new feature of Aspose Cells and will be released in 20.11.0 too? Because if it’s true, we must change a lot of source code in our project.

Thank you.

7

@dunghnguyen,

CollectionBase is only kept in Aspose.Cells for .Net4.0 library from now onwards. It has been made invisible in NET 2.0. If you need to use CollectionBase, you should use Net3.5 or above version.

8

The issues you have found earlier (filed as CELLSNET-47675) have been fixed in this update. This message was posted using Bugs notification tool by simon.zhao