You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 9, 2020. It is now read-only.
We migrated from 4.1.1.0 to 4.5.3.2 and can no longer read custom properties that are Int64/long data types.
On creation of the Excel file: package.Workbook.Properties.SetCustomPropertyValue("Timestamp", DateTime.Now.Ticks);
On reading of the Excel file (with changes to the Excel file): DateTime timestamp = new DateTime(Convert.ToInt64(package.Workbook.Properties.GetCustomPropertyValue("Timestamp")));
Always results in null, even though the CustomPropertiesXml contains a valid value:
using System;
public class Program
{
public static void Main()
{
Console.WriteLine(new DateTime(Convert.ToInt64(6.37115722044558E+17)));
// returns 12/10/2019 10:56:44 AM
}
}
If we create the Excel file and immediately try to read it (without making any changes to it), the custom property is read successfully.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We migrated from 4.1.1.0 to 4.5.3.2 and can no longer read custom properties that are Int64/long data types.
On creation of the Excel file:
package.Workbook.Properties.SetCustomPropertyValue("Timestamp", DateTime.Now.Ticks);
On reading of the Excel file (with changes to the Excel file):
DateTime timestamp = new DateTime(Convert.ToInt64(package.Workbook.Properties.GetCustomPropertyValue("Timestamp")));
Always results in null, even though the CustomPropertiesXml contains a valid value:
DotNetFiddle:
If we create the Excel file and immediately try to read it (without making any changes to it), the custom property is read successfully.
The text was updated successfully, but these errors were encountered: