Thank you for this nice library .
There is an issue with guide data type as it returns error "can't convert System.guide to string"
to solve this issue we have to change ExcelExportEngine line 255 to use convert.ToString(propValue) instead of direct string casting (string)
var cellValue = Convert.ToString(propValue); (this will solve guide casting issue )
instead of
var cellValue = (string)propValue; (this will return error with guide)

Regards,

Could not load file or assembly 'Infodinamica.Framework.Core, Version=3.2.0.29908, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

at Infodinamica.Framework.Exportable.Tools.MetadataHelper.GetHeadersFormat(Type type)
at Infodinamica.Framework.Exportable.Engines.Excel.ExcelExportEngine.CreateSheet(KeyValuePair`2 excelSheet)
at Infodinamica.Framework.Exportable.Engines.Excel.ExcelExportEngine.Export()

Hi,

Great project, I love it!
I encountered the issue of being unable to open the generated XLSX with Excel 2019, the error stating file was corrupted. However, updating NPOI and SharpZipLib packages to their latest versions (NPOI version 2.4.1 and SharpZipLib version1.2.0) resolved the issue for me, so I thought it'd be good idea for you to update them in repo, too.

Cheers,
Antonia

How I can change header color before export with “IExportEngine”

Naming the column's name attribute with the same name generates an exception.

Example: (For the sake of the simplicity I be cut off some part of the class content )

[ExportableExcelHeader(BackColor = "#FF0000", BorderColor = "#FF0000", FontName = "Calibri")]
    public class ShipmentFileExport
    {
 .........

       
        [Exportable(7, "Nombre*", FieldValueType.Text)]
        public string NombreDestinatario { get; set; }

        [Exportable(8, "Apellido *", FieldValueType.Text)]
        public string ApellidoDestinatario { get; set; }

        [Exportable(9, "DNI", FieldValueType.Numeric)]
        public int DniDestinatario { get; set; }

        [Exportable(10, "Email", FieldValueType.Text)]
        public string EmailDestinatario { get; set; }

.........

       [Exportable(21, "Nombre *", FieldValueType.Text)]
        public string NombreRemitente { get; set; }

        [Exportable(22, "Apellido *", FieldValueType.Text)]
        public string ApellidoRemitente { get; set; }

        [Exportable(23, "DNI", FieldValueType.Numeric)]
        public int DniRemitente { get; set; }

        [Exportable(24, "Email *", FieldValueType.Text)]
        public string EmailRemitente { get; set; }
}

After cloning the repository and running the unit tests, I see that all the tests fail.

Debugging, I see that there is a test destination route that is harked.
My suggestion would be, would not it be advisable to return this parameterizable path?

Thinking in cases when an Excel Sheet has two lines of Header (Header ---merged cells --- and SubHeader as a column name) would be nice.

For Reference:
https://stackoverflow.com/questions/28143102/exporting-data-to-excel-using-npoi-in-c-sharp/33813474#33813474

(Second example Datasource -> Excel)