OssianEPPlus
OssianEPPlus
Reconsider our handling of "Alternate Content Roundtripping" in accordance with ooxml standard As in dataValidations s463 file. This occurs in excel when entering decimals with commas in a list validation...
When copying data validations, EPPlus iterates all data validation items in the worksheet to see if the address matches the copied range this has devestating effects on performance when a...
When reading a file in 7.0.6 or higher from a file saved with an earlier version of epplus containing dataValidation Lists (Dropdowns) only the first is read and the rest...
The current HTMLExporter and thereby WebSamples project does not have support for the new conditionalFormatting functionality added in Epplus7.
Our internal collide function only appears to handle the first address if the two addresses is a comma-separated excelAddress. Resulting in collision: None if two comma-separated addresses have the same...
Currently ExcelAddress.Adresses is internal and does not seem to update appropriately in some cases (ConditionalFormatting when read at least) This makes it overly complex to add a row to both...
Saving a package and then attempting to add data to this closed package and saving again may cause corrupt workbooks as other internal files e.g. Styles may still be written...
Multiple areas in Epplus use Decimal rather than double for no apparent reason even when excel uses doubles. A few examples are: - ExcelChartTrendline.cs which uses it for many properties:...
When Epplus writes worksheet attributes such as xmlns:xr and xmlns:x14ac they must also be in mc:Ignorable to ensure the xml is fully valid. This should be handled dynamically so that...
Fix for #1432