Skip to content

Releases: ClosedXML/ClosedXML.Report

0.2.12

22 May 21:28

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 0.2.11...0.2.12

0.2.12-rc

26 Feb 20:25
d483683

Choose a tag to compare

0.2.12-rc Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: 0.2.11...0.2.12-rc

0.2.11

26 Feb 20:21
fd6e29a

Choose a tag to compare

What's Changed

  • Add disabled parameter to "Delete" tag and evaluate values before parsing by @vakssonya in #358
  • Add Height and HeightRange option. by @masterworgen in #360
  • Bump System.Linq.Dynamic.Core from 1.3.8 to 1.6.0.1 #376 by @jafin in #377
  • upgrade_Version_ClosedXML_102.3 by @ToggyO in #366

New Contributors

Full Changelog: 0.2.10...0.2.11

0.2.10

11 Apr 06:39
7dbb3bb

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 0.2.9...0.2.10

v.0.2.9

12 Feb 12:50
8b795ea

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 0.2.8...0.2.9

v.0.2.8

26 Jul 13:51
a530ce9

Choose a tag to compare

Mostly a technical release to enable usage of ClosedXML.Report for those who is using ClosedXML 0.101.

Version 0.101 has many improvements so the new version of ClosedXML.Report will also benefit from them.

Also, after ClosedXML, target netstandard2.0 and netstandard2.1, rather than building different versions for each framework.

What's Changed

Full Changelog: 0.2.7...0.2.8

v.0.2.7

26 Jul 12:56
c06aae2

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 0.2.6...0.2.7

Breaking changes

Upgrading to ClosedXML 0.100 broke one piece of functionality: previously it was possible to put a <<sum>> tag into a formula, e.g. &="Total:"<<sum>>. After the upgrade, this became hard to implement without major refactoring. Given that none of the contributors have enough time to perform such kind of refactoring and that this functionality has not been documented - I decided, it is better to drop it and release a new version we all have been waiting by far too long.

v.0.2.6

07 Jan 09:51
1a925c2

Choose a tag to compare

This is a purely technical though long requested release upgrading ClosedXML to version 0.97 where dependencies on System.Drawing.Common were removed, as well as many other cool things happened.

What's Changed

v.0.2.5

07 Jan 09:31

Choose a tag to compare

Breaking changes

  • ClosedXML.Report became signed which made ClosedXML.Report.Signed package deprecated.
  • ClosedXML upgraded to 0.96 which in turn had some breaking changes

What's Changed

  • issue with Simple Template address #196 by @b0bi79 in #238
  • Fixed a performance issue caused by a large number of merged ranges. … by @b0bi79 in #247
  • 95 nullreferenceexception with rows fit by @b0bi79 in #254
  • #255 Unable to use "over" when using <> by @b0bi79 in #256
  • Subtotal for column specific formula by @srihar in #265
  • Adding IXLTemplate interface by @davija in #269
  • refactor: tests, bump target to netstandard2.0;net462;net6.0, move test data into sqlite. by @jafin in #274
  • fix: do not throw when access null item property by @GersonDias in #290
  • Update to ClosedXML version 0.96; drop ClosedXML.Report.Signed by @pallu in #286

New Contributors

Full Changelog: https://github.com/ClosedXML/ClosedXML.Report/milestone/11?closed=1

Nuget packages:
https://www.nuget.org/packages/ClosedXML.Report/0.2.5

v0.2.4

21 Aug 16:28

Choose a tag to compare

Release notes:

  • Fixed updating the size of the resulted range. The error led to the appearance of the empty data in the pivot tables (#230)
  • Fixed filling of images in the horizontal range (#233)
  • Fixed Merged ranges calculations (#233)
  • Fixed propagation of row heights from template to generated rows (#233)
  • Added examples with hyperlinks (#234)
  • Fixed unexpected merging while using <<group MergeLabels=Merge2>> in nested groups?(#235)

Complete list of closed issues

Nuget packages:
https://www.nuget.org/packages/ClosedXML.Report/0.2.4
https://www.nuget.org/packages/ClosedXML.Report.Signed/0.2.4