Free Support Forum - aspose.com

Can't save xlsx file to html

Hi, i’m trying to save this xlsx file to html format and facing an issue.
The programm is trying to do it during a long time and eating a lot of memory (file is small), but can’t finish.
I think that it’s related with a table formating of whole sheet. But MS Excel is converting this file to html very fast (reducing empty rows at the end of sheet).
Source file:
TEST.zip (10.0 KB)

C# code sample:
Workbook wb = new Workbook(@“C:\TEST.xlsx”, new LoadOptions() { MemorySetting = MemorySetting.MemoryPreference });
HtmlSaveOptions so = new HtmlSaveOptions(SaveFormat.Html);
wb.Save(@“C:\TEST.html”, so);
How can I convert such file to html?
Thank you.

@qqflyqq,

We were able to observe the issue but we need to look into it more. We have logged the issue in our database for investigation and for a fix. Once, we will have some news for you, we will update you in this topic.

This issue has been logged as

CELLSNET-46251 - Application hangs while converting XLSX to HTML

@qqflyqq,

Please find attached our latest version/fix: Aspose.Cells for .NET v18.7.4 (.NET 2.0 and .NET 4.0)

Your issue should be fixed in it.

Let us know your feedback.
Aspose.Cells18.7.4 For .Net2_AuthenticodeSigned.Zip (3.8 MB)
Aspose.Cells18.7.4 For .Net4.0.Zip (3.8 MB)

Thank you, it works nice now!
How soon we can get version with this fix from NuGet?

@qqflyqq

We only publish official releases on Nuget\maven repos. The hotfix, i.e., Aspose.Cells for .NET v18.7.4 is fully tested and includes all the features (full fledged) and previous fixes and enhancements, so you may use it on production server. It is safe to use the hotfix on the server. However, if you still want the version to be uploaded onto Nuget, then you have to wait for our next official release of the product. We will publish our next official release, i.e., Aspose.Cells for .NET v18.8 (which will also include your fix) in the third week of August, 2018.

1 Like

The issues you have found earlier (filed as CELLSNET-46251) have been fixed in this update. This message was posted using BugNotificationTool from Downloads module by Amjad_Sahi