All Versions
15
Latest Version
Avg Release Cycle
57 days
Latest Release
1312 days ago

Changelog History
Page 2

  • v4.11.0

    June 07, 2019
  • v4.10.1

    May 22, 2019
  • v4.10.0

    March 28, 2019
  • v4.9.0

    January 03, 2019
  • v4.8.1.1 Changes

    October 02, 2018

    ๐Ÿš€ I am pleased to announce the release of CSLA .NET version 4.8.1.

    ๐Ÿฑ ๐Ÿ›‘ This is a big change, because I was able to eliminate the CSLA-Core-NS package. If you are using the CSLA-Core-NS package you will need to remove that reference and add a reference to the CSLA-Core package.

    โšก๏ธ โš  If you have any custom rules (subclass of BusinessRule or implement IBusinessRule you will need to update all Execute methods to accept an IRuleContext parameter instead of a RuleContext parameter.

    ๐Ÿ›  There are a number of other changes and bug fixes including:

    From 4.8.1:

    • #946 Fix NullReferenceException in DataPortalException.BusinessException

    From 4.8.0:

    • ๐Ÿ“ฆ #927 Eliminate CSLA-Core-NS package ๐Ÿ›‘
    • #703 Allow use of BinaryFormatter in .NET Standard 2.0 and .NET Core
    • #344 Stop caching DisplayName value so localization works as expected โš 
    • 0๏ธโƒฃ #344 Ensure string properties default to String.Empty not null โš 
    • #827 Eliminate NullReferenceException in Rule.Complete โš 
    • #340 Enable per-type authz rules when passing interface types to the data portal
    • 0๏ธโƒฃ #917 Fix issue with non-default timeout in HttpProxy
    • ๐Ÿšš #635 Move wiki to the /docs directory so it is part of the repo
    • ๐Ÿ‘ป #650 Better exception when incorrect CslaDataPortalProxy is specified
    • #938 Simplify version numbering so we can start using semver
    • โš  #914 WARNING 0xdef01051 No default or neutral resource given for UWP

    ๐Ÿ‘€ You can see all the closed work items in GitHub.

    ๐Ÿš€ ๐Ÿ’ก After this release I'll start officially using the semver (semantic versioning) concept, so breaking changes will be more clearly noted via version changes. In this release I've started that process by using a .0 instead of .100 for the patch number.