Version 6.1.0 release

CSLA 6 releases

CSLA 6 is a major new version of CSLA .NET, fully supporting (and requiring) dependency injection and other features of modern .NET.

CSLA .NET version 6.1.0 release

CSLA .NET version 6.1.0 adds support for Maui and includes bug fixes and one breaking change.

• #2549 Add UI helpers for Maui
• #2672 Enhance PropertyChanged behavior in Csla.Xaml.ViewModelBase
• #2764 Update snippets NuGet installer for VS2022
• #2922 Blazor no longer requires text-based serialization
• #2946 LocalProxy now properly disposes DI scope and dependencies
• #2953 DataAnnotations rules now support DI
• #2957 Child data portal expections now flow up with details
• #2981 You can now get a System.Reflection.PropertyInfo from Csla.Blazor.PropertyInfo
• #3007 Add new BlazorServerExample project to the Samples folder
• #3014 Fix bug in child data portal
• #3025 Fix issue with analyzers

Change List

• Changes in this release
• Breaking changes

Dependency Updates

• Grpc.Net.Client
• Grpc.Tools
• Newtonsoft.Json
• RabbitMQ.Client
• Microsoft.NETCore.UniversalWindowsPlatform
• Xamarin.Forms
• Microsoft.AspNet.WebApi.Client
• Microsoft.AspNet.WebPages
• Microsoft.Web.Infrastructure
• Microsoft.AspNet.WebApi.Core
• Microsoft.AspNet.Mvc
• Microsoft.AspNet.Razor
• Google.Protobuf
• Microsoft.CodeAnalysis.CSharp

Contributors

@joshhanson314
@rockfordlhotka
@TheCakeMonster
@JasonBock

CSLA .NET version 6.0.0 release

CSLA .NET version 6.0.0 is a major release with numerous breaking changes, including:

• Business domain types must have a public constructor
• Public constructors for many types will have parameters provided via depedency injection
• Support for .NET 4.0 and 4.5 has been dropped; .NET 4.6.2 is the minimum required
• The data and object context managers in Csla.Data have been removed in favor of using dependency injection

This version supports:

• .NET 6
• .NET Framework 4.6.2 to 4.8
• netstandard 2.0 and 2.1
• Blazor
• Xamarin
• mono

Operating Systems and Platforms:

• Windows (servers and UWP, WPF, Windows Forms)
• Linux (servers and Xamarin)
• iOS and Android (Xamarin)
• Mac (servers and Xamarin)
• Kubernetes and other container-based runtimes
• ASP.NET Core and ASP.NET 5
• Other client and server environments where .NET Core or mono are available

Change List

• Changes in this release
• Breaking changes.

Upgrade documentation

There is a document describing common issues people will likely encounter when upgrading from CSLA 5 to CSLA 6.

• Upgrading to CSLA 6

Contributors

The CSLA community is fantastic! The people who've submitted bugs, helped think through solutions, lobbied for features and enhancements, and submitted pull requests are listed below.

@455986780
@adrianwright109
@ajohnstone-ks
@Art666OTS
@BaHXeLiSiHg
@coder-rr
@danielmartind
@dazinator
@devcs21
@dotMorten
@Eduardo-Micromust
@GreatBarrier86
@j055
@JacoJordaan
@JasonBock
@jhnsartain3
@jonparker
@joshhanson314
@kellyethridge
@michaelcsikos
@MTantos1
@peranborkett
@poepoe12002
@ProDInfo
@RaviPatelTheOne
@rfcdejong
@rockfordlhotka
@russblair
@SachinPNikam
@swegele
@TheCakeMonster

Thank you all so much for your support!

Version 6.0.0 release

CSLA 6 is a major new version of CSLA .NET, fully supporting (and requiring) dependency injection and other features of modern .NET.

Version 6.0.0 includes numerous breaking changes, including:

• Business domain types must have a public constructor
• Public constructors for many types will have parameters provided via depedency injection
• Support for .NET 4.0 and 4.5 has been dropped; .NET 4.6.2 is the minimum required
• The data and object context managers in Csla.Data have been removed in favor of using dependency injection

This version supports:

• .NET 6
• .NET Framework 4.6.2 to 4.8
• netstandard 2.0 and 2.1
• Blazor
• Xamarin
• mono

Operating Systems and Platforms:

• Windows (servers and UWP, WPF, Windows Forms)
• Linux (servers and Xamarin)
• iOS and Android (Xamarin)
• Mac (servers and Xamarin)
• Kubernetes and other container-based runtimes
• ASP.NET Core and ASP.NET 5
• Other client and server environments where .NET Core or mono are available

Change List

• Changes in this release
• Breaking changes.

Upgrade documentation

There is a document describing common issues people will likely encounter when upgrading from CSLA 5 to CSLA 6.

• Upgrading to CSLA 6

Contributors

The CSLA community is fantastic! The people who've submitted bugs, helped think through solutions, lobbied for features and enhancements, and submitted pull requests are listed below.

@455986780
@adrianwright109
@ajohnstone-ks
@Art666OTS
@BaHXeLiSiHg
@coder-rr
@danielmartind
@dazinator
@devcs21
@dotMorten
@Eduardo-Micromust
@GreatBarrier86
@j055
@JacoJordaan
@JasonBock
@jhnsartain3
@jonparker
@joshhanson314
@kellyethridge
@michaelcsikos
@MTantos1
@peranborkett
@poepoe12002
@ProDInfo
@RaviPatelTheOne
@rfcdejong
@rockfordlhotka
@russblair
@SachinPNikam
@swegele
@TheCakeMonster

Thank you all so much for your support!

Version 5.5.3 release

Version 5.5.3 contains bug fixes over v5.5.2.

🛑 🔐 Security warning: This version of CSLA .NET allows the use of WcfProxy. WcfProxy uses the NetDataContractSerializer (NDCS) which has known vulnerabilities that can allow remote execution of code during deserialization. NDCS itself is considered obsolete, and you should avoid using WcfProxy or upgrade to CSLA 6 or higher where this issue does not exist.

Here is a list of all changes.

Highlights:

• Backport feature to run all business rules on server-side data portal (optional)
• Fix long-standing issue with System.Runtime.Loader dependency
• Implement no-param fallback for UpdateChild data portal operation

Many thanks to:

• @TheCakeMonster
• @GreatBarrier86
• @niijyeni
• @Eduardo-Micromust

Version 5.5.2 release

This is a bug fix release over version 5.5.1.

🛑 🔐 Security warning: This version of CSLA .NET allows the use of WcfProxy. WcfProxy uses the NetDataContractSerializer (NDCS) which has known vulnerabilities that can allow remote execution of code during deserialization. NDCS itself is considered obsolete, and you should avoid using WcfProxy or upgrade to CSLA 6 or higher where this issue does not exist.

Here is a list of the changes

Version 5.5.1 release

Bug fixes over the 5.5.0 release.

🛑 🔐 Security warning: This version of CSLA .NET allows the use of WcfProxy. WcfProxy uses the NetDataContractSerializer (NDCS) which has known vulnerabilities that can allow remote execution of code during deserialization. NDCS itself is considered obsolete, and you should avoid using WcfProxy or upgrade to CSLA 6 or higher where this issue does not exist.

Change List

Changes in this release

Contributors

• @RaviPatelTheOne
• @amselem
• @rockfordlhotka

Version 5.5.0 release

Enhancements and Bug fixes over the 5.4.2 release.

🛑 🔐 Security warning: This version of CSLA .NET allows the use of WcfProxy. WcfProxy uses the NetDataContractSerializer (NDCS) which has known vulnerabilities that can allow remote execution of code during deserialization. NDCS itself is considered obsolete, and you should avoid using WcfProxy or upgrade to CSLA 6 or higher where this issue does not exist.

Changes in this release

• #2095 🎉 Add support for unloading assemblies from memory (re: caching)
• #2377 🐜 Add missing LoadListMode implementation for some list types
• #2347 🐜 Remove Console.WriteLine statement in Blazor ViewModel
• #2302 🐜 n-level undo causing exception with SortedBindingList
• #2287 🐜 Private data portal method not found from base classes
• #2303 🐜 [DeleteSelfChild] cannot be parameterless; requires parameters that match DataPortal.UpdateChild(...)

Contributors

• @michaelcsikos
• @ProDInfo
• @BaHXeLiSiHg
• @ajohnstone-ks

Version 5.4.2 release

Bug fixes over the 5.4.1 release.

🛑 🔐 Security warning: This version of CSLA .NET allows the use of WcfProxy. WcfProxy uses the NetDataContractSerializer (NDCS) which has known vulnerabilities that can allow remote execution of code during deserialization. NDCS itself is considered obsolete, and you should avoid using WcfProxy or upgrade to CSLA 6 or higher where this issue does not exist.

Change List

Changes in this release

• #2161 🐜 Fix Blazor WebAssembly loses ApplicationContext values
• #2109 🐜 Fix AmbiguousMatchException DataPortal.Fetch
• #2075 🐜 HttpProxy compression code doesn't work with custom HttpClient

Contributors

• @rockfordlhotka
• @coder-rr

Version 5.4.1 release

The version 5.4.1 release contains bug fixes over the 5.4.0 release.

🛑 🔐 Security warning: This version of CSLA .NET allows the use of WcfProxy. WcfProxy uses the NetDataContractSerializer (NDCS) which has known vulnerabilities that can allow remote execution of code during deserialization. NDCS itself is considered obsolete, and you should avoid using WcfProxy or upgrade to CSLA 6 or higher where this issue does not exist.

Change List

Changes in this release

Contributors

• @ajohnstone-ks
• @joshhanson314
• @j055
• @rockfordlhotka
• @adrianwright109
• @kellyethridge
• @rfcdejong
• @russblair

Version 5.4.0 release

The 5.4.0 release of CSLA .NET adds support for .NET 5 across all supported scenarios, including:

• Blazor
• aspnetcore
• Windows Forms
• WPF

🛑 🔐 Security warning: This version of CSLA .NET allows the use of WcfProxy. WcfProxy uses the NetDataContractSerializer (NDCS) which has known vulnerabilities that can allow remote execution of code during deserialization. NDCS itself is considered obsolete, and you should avoid using WcfProxy or upgrade to CSLA 6 or higher where this issue does not exist.

The release notes doc contains more details.

Change List

Changes in this release

Contributors

• @BlagoCuljak Compression in Http data portal channel
• @dazinator DI enhancements
• @danielmartind RabbitMQ updates, dependency updates, bug fixes
• @rockfordlhotka Enhancements
• @richardbartley Bug reports/research
• @brinawebb Bug reports
• @richardbartley Bug reports/research

Version 4.11.2 release

I am pleased to announce the release of CSLA .NET version 4.11.2.

This is a bug fix release from 4.11.1.

🛑 🔐 Security warning: This version of CSLA .NET allows the use of WcfProxy. WcfProxy uses the NetDataContractSerializer (NDCS) which has known vulnerabilities that can allow remote execution of code during deserialization. NDCS itself is considered obsolete, and you should avoid using WcfProxy or upgrade to CSLA 6 or higher where this issue does not exist.

• #1212 Fix issue with n-level undo and cloning

CSLA .NET version 4.11.1 Release Notes

I am pleased to announce the release of CSLA .NET version 4.11.1.

This is a bug fix release from 4.11.0.

• #1138 Backport fix for TransactionTypes enum issue

CSLA .NET version 4.11.0 Release Notes

I am pleased to announce the release of CSLA .NET version 4.11.0.

This is an enhancement and bug fix release from 4.10.1.

• #1164 Fix issue where LocalProxy would lock a Windows Forms app using async data portal calls
• #1167 Add UpdateAllChildren method to FieldManager to simplify saving all child objects regardless of their IsDirty value

CSLA .NET version 4.10.1 Release Notes

I am pleased to announce the release of CSLA .NET version 4.10.1.

This is a bug fix release from 4.10.0.

• #1130 Backport SimpleDataPortal async mismatch check fix #1117 and fix for explicit null default values for string properties to version 4.x #1103
• #1155 Backport fix for Blazor scenario with HttpProxy to autoflush text writer

CSLA .NET version 4.10.0 Release Notes

I am pleased to announce the release of CSLA .NET version 4.10.0.

This is a bug fix release from 4.9.0.

• #1084 Backport sync context changes from v5.0

CSLA .NET version 4.9.0 Release Notes

The major enhancements are described in some detail in a CSLA .NET 4.9.0 blog post.

Dependabot and NuGet dependencies

We've started using Dependabot to help keep NuGet dependencies current. As a result, the following updates are included in this release:

• Bump Microsoft.AspNet.Razor from 2.0.20710 to 2.0.30506 in /Source
• Bump Microsoft.EntityFrameworkCore from 2.1.4 to 2.2.0 in /Source
• Bump System.Data.SqlClient from 4.5.1 to 4.6.0 in /Source
• Bump Xamarin.Forms from 3.0.0.482510 to 3.4.0.1008975 in /Source
• Bump Microsoft.EntityFrameworkCore from 2.0.2 to 2.1.4 in /Source
• Bump System.Security.Principal.Windows from 4.5.0 to 4.5.1 in /Source
• Bump System.Data.SqlClient from 4.4.3 to 4.5.1 in /Source
• Bump Microsoft.AspNetCore from 2.0.2 to 2.1.6 in /Source
• Bump Microsoft.AspNet.WebPages from 2.0.20710 to 3.2.7 in /Source
• Bump System.ComponentModel.Annotations from 4.4.1 to 4.5.0 in /Source
• [Security] Bump Microsoft.NETCore.UniversalWindowsPlatform

Docs and wiki

We've updated some of the docs and officially removed the wiki. All the wiki/docs content is now in the /docs directory.

Data portal enhancements

• #993 Implement SaveAndMergeAsync methods
• #972 Implement data portal router
• #959 Enhance data portal to use different endpoint per business type
• #961 Create data portal health/instrumentation endpoint
• #1011 Implement IsOffline property for data portal
• #982 Add new IDataPortalFactory singleton for page injection in ASP.NET Core

Configuration enhancements

• #966 Add fluent config types to CSLA: Csla.Configuration.CslaConfiguration
• #967 Read CSLA config values from .NET Core config subsystem: CslaConfigurationOptions
• #1012 Implement ConfigureCsla extension method to IConfiguration for use in .NET Core configuration
• #982 Implement AddCsla method for use in ASP.NET Core ConfigureServices

Bug fixes

• #949 [samples] Fix WinForms and WPF DataPortal configuration to use Azure
• #956 [bug] Check for null User in authz rules
• #962 [bug] Object not serializable (Csla.Core.ContextDictionary) after compiled with .Net Native tool chain and Optimize Code Enabled

You can see all the closed work items in GitHub.