ExportDataTable doesn´t use current culture for double to string conversion

The ExportDataTable function does convert a double value wrong to string if the current thread does use german culture settings.

The ExportDataTableAsString function does use the current culture setting.

For example a double value 1.56 need to get converted as string with comma as decimal seperator:

The ExportDataTable does return “1.56”

Please find attached an example project. It does use latest Aspose.Cell binaries.

AsposeTestApp.zip (6.0 MB)


After an initial testing, I am able to reproduce the issue as you mentioned by using your sample code segment. I found ExportDataTable does not use current culture for double to string conversion. It seems expected behavior for ExportDataTable method but we need to evaluate it in details.

We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CELLSNET-56116

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

We are pleased to inform you that your issue (“CELLSNET-56116”) has been resolved. The fix/enhancement will be included in our upcoming release (Aspose.Cells v24.7) which is due in the second week of July this month. You will be notified when the next version is released.

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