ByteSize changelog

Changelog History

• v2.0.0

  January 14, 2020

  HUGE BREAKING CHANGE :

  0️⃣ By default ByteSize now assumes 1 KB == 1000 B and 1 KiB == 1024 B to
  adhere to the IEC and NIST standards (https://en.wikipedia.org/wiki/Binary_prefix).
  ⬆️ In the past ByteSize assumed 1 KB == 1024 B, that means if you're upgrading
  👀 from v1, you'll see differences in values.

  Other Breaking Changes:

  • 📇 Renamed property LargestWholeNumberSymbol and LargestWholeNumberValue to LargestWholeNumberDecimalSymbol and LargestWholeNumberDecimalValue respectively.
  • Drop support for all platforms except netstandard1.0 and net45.

  🆕 New Features:

  • 👌 Support for binary and decimal values (e.g. ByteSize.FromKibiByte and ByteSize.FromKiloByte). (#24 by @omar)
  • 🆕 New constructor that takes a long value as the number of bits.
  • 👌 Support for culture on Parse and TryParse. (#39 by @P-Storm)

• v2.0.0-beta1

  June 16, 2019

• v2.0.0-alpha2

  March 28, 2019

• v2.0.0-alpha1

  March 28, 2019

• v1.3.0

  January 22, 2017

  • ➕ Add support for subtracting two ByteSize objects. (#25 by @omar)

• v1.2.5

  January 21, 2017

  • 👍 Properly support .NET Standard 1.0. (#29 by @jp7677)

• v1.2.4

  November 25, 2016

  • 🛠 Fix TryParse to not throw exceptions. (#23 by @omar)

• v1.2.3

  November 10, 2016

  • 🛠 Fix ByteSize of zero ToString output. (#21 by @omar)

• v1.2.2

  October 28, 2016

  • 👌 Improve memory footprint of a ByteSize object. (#20 by @atifaziz)

• v1.2.1

  July 23, 2016

  • 🛠 Fix parsing of numbers with group number separator like 1,500.65 mb. (#17 by @omar)