Build 3.0.0.151 of xlsgen ensures that a client application can lock/unlock entire columns or rows, not just individual cells.

Build 3.0.0.150 of xlsgen has a fix related to rendering numbers. It has to do with some of the weird behaviors in Excel that xlsgen is supposed to mimic otherwise it will be seen as a bug. So depending on whether cells around a given cell are empty or not, depending on whether the cell is filled with a number seen as a number (decimal part, ...) or as nothing special (General), what gets displayed is different (how many decimals are actually displayed, is there a clipping effect on the right, is the alignment on the left, is there a round up of decimals, ...).

Build 3.0.0.149 of xlsgen changes how columns are rendered (print, preview, PDF, ...). The effect is that more content can be displayed in the same page (i.e. less pages are used if you output the spreadsheet).

Build 3.0.0.148 of xlsgen uses local time (WIN32 API call) in the calculation engine as well as calculated members such as header/footer datetime. Before this build, xlsgen was using system time (another WIN32 API call) thinking that this always returned the correct time, and turns out it does not. We would get up to two hours difference by using the system time.

Build 3.0.0.147 of xlsgen has a fix related to parsing header/footer for rendering purposes. End of lines were not handled correctly, they were getting doubled as a an artefact of handling both Unix-like and Windows-like end of lines.

Build 3.0.0.146 of xlsgen has a fix related to rendering cells (print, preview, PDF, ...). Better handling of cells with "no fill" formatting. This is now really transparent.