Skip to content

Releases: csf-dev/CSF.Utils

v7.0.1

21 Aug 18:34

Choose a tag to compare

This is a backwards-compatible bugfix release.

Changelog

  • Resolve #127 - Two functions were intended to be extension methods but were not
  • Minor build improvements for Linux - solution no longer requires Mono

v7.0.0

02 Apr 19:27

Choose a tag to compare

This is an almost complete rewrite of the functionality within this repository.

Changelog

  • Much functionality has been removed; for one of two reasons:
  • The remaining functionality has been split up into three separate packages
  • The packages are now multi-targeted across a number of netstandard environments as well as net45

v6.1.1

28 Apr 12:38

Choose a tag to compare

This is a single-issue release to deal with a failure in strong-naming the assembly. This was caused by mono/mono#8495

v6.1.0

15 Apr 11:13

Choose a tag to compare

This is a feature-enhancement and bugfix release. As well as the changelog below, this marks the first release in which the assembly is strongly-named using a signing key.

Changelog

  • #105 - Add array-copying functionality
  • #107 - Fix GetHashCode implementation
  • #109 - Add functionality to manipulate filenames and extensions
  • #110 - Deprecate exception extensions (superseded by FCL functionality)

v6.0.0

07 Dec 19:43

Choose a tag to compare

This release is largely the same as v5.0.0, except that all other projects have been removed from this solution & repository.

v5.0.0

05 Dec 19:26

Choose a tag to compare

This release breaks the CSF utilities solution apart into many separate projects/assemblies. It is a halfway-point for migration towards separating the various components of this library into totally separate solutions/repositories.

This release is obsolete and unsupported. Please do not use it for any production-grade work.

v4.1.1

05 Dec 19:14

Choose a tag to compare

This is the last main release which will support all of the separate components of CSF utilities as a single project/assembly. As of v5 and onwards, the functionality of this solution will be split into separate projects, with a view towards them being broken into totally independent solutions/repositories as of v6 and onwards.

This release is obsolete; do not use it for any new production-grade work.