Build 4.5.0.2 of xlsgen adds support for Unicode-based CSV files. Those files are encoded using either Unicode UCS2 (i.e. fix 2-byte characters), or Unicode UTF-8 (i.e. variable length character size, neutrally convertible to Unicode UCS2 and vice versa).

The interesting bit is that it is automatically detected when a CSV file is submitted to xlsgen for opening/importing. So there is no need to know in advance that the CSV file (or buffer) is encoded with Unicode or not, and there is no need to set the corresponding CSV import option (by the way, only the UTF8 option is available in the xlsgen object model, so even if you knew that your CSV file was encoded using Unicode UCS2, there was no mechanism to make xlsgen read it).

This adds up to the arsenal of automatic inference tooling in xlsgen.

Build 4.5.0.1 of xlsgen fixes a problem related to deleting columns (worksheet.Columns("A:F").Delete(); for instance). Under certain circumstances, xlsgen could write back the resulting file with negative column indexes, and Excel would identify this as a file corruption problem.