Releases: MarimerLLC/csla
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.WcfProxyuses 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 usingWcfProxyor upgrade to CSLA 6 or higher where this issue does not exist.
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.WcfProxyuses 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 usingWcfProxyor upgrade to CSLA 6 or higher where this issue does not exist.
Change List
Contributors
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.WcfProxyuses 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 usingWcfProxyor upgrade to CSLA 6 or higher where this issue does not exist.
- #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
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.WcfProxyuses 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 usingWcfProxyor upgrade to CSLA 6 or higher where this issue does not exist.
Change List
- #2161 🐜 Fix Blazor WebAssembly loses ApplicationContext values
- #2109 🐜 Fix AmbiguousMatchException DataPortal.Fetch
- #2075 🐜 HttpProxy compression code doesn't work with custom HttpClient
Contributors
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.WcfProxyuses 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 usingWcfProxyor upgrade to CSLA 6 or higher where this issue does not exist.
Change List
Contributors
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.WcfProxyuses 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 usingWcfProxyor upgrade to CSLA 6 or higher where this issue does not exist.
The release notes doc contains more details.
Change List
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.WcfProxyuses 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 usingWcfProxyor 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
LocalProxywould lock a Windows Forms app using async data portal calls - #1167 Add
UpdateAllChildrenmethod toFieldManagerto simplify saving all child objects regardless of theirIsDirtyvalue
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
HttpProxyto 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
SaveAndMergeAsyncmethods - #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
IsOfflineproperty for data portal - #982 Add new
IDataPortalFactorysingleton 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
ConfigureCslaextension method toIConfigurationfor use in .NET Core configuration - #982 Implement
AddCslamethod for use in ASP.NET CoreConfigureServices
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.
Version 4.8.1 release
I am pleased to announce the release of CSLA .NET version 4.8.1.
🛑 🔐 Security warning: This version of CSLA .NET allows the use of
WcfProxy.WcfProxyuses 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 usingWcfProxyor upgrade to CSLA 6 or higher where this issue does not exist.
🛑 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-NSpackage 🛑 - #703 Allow use of
BinaryFormatterin .NET Standard 2.0 and .NET Core - #344 Stop caching
DisplayNamevalue so localization works as expected ⚠ - #344 Ensure string properties default to
String.Emptynotnull⚠ - #827 Eliminate
NullReferenceExceptioninRule.Complete⚠ - #340 Enable per-type authz rules when passing interface types to the data portal
- #917 Fix issue with non-default timeout in
HttpProxy - #635 Move wiki to the
/docsdirectory 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.
Version 4.7.200 release
I am pleased to announce the release of CSLA .NET version 4.7.200 with support for Blazor, and enhanced support for ASP.NET Core and Xamarin.
The packages are now in NuGet.
🛑 🔐 Security warning: This version of CSLA .NET allows the use of
WcfProxy.WcfProxyuses 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 usingWcfProxyor upgrade to CSLA 6 or higher where this issue does not exist.
This is a pretty big release, focused on four key areas:
- Improved sample code
- Enhanced support for ASP.NET Core
- The new
CslaModelBinderProviderandCslaModelBindertypes support data binding in Razor Pages scenarios
- The new
- Enhanced support for Xamarin
- Updated for Xamarin Forms 3.0; Enhanced the
PropertyInfotype, Fixed critical bug inGraphMergeron iOS
- Updated for Xamarin Forms 3.0; Enhanced the
- Support for Blazor (and mono/wasm)
- Add support for Blazor so it is possible to use CSLA objects in client-side mono/wasm code in a Blazor app, reference the
CSLA-Core-NSpackage from your Blazor client app to use CSLA
- Add support for Blazor so it is possible to use CSLA objects in client-side mono/wasm code in a Blazor app, reference the
More details are listed here:
ASP.NET Core
- #900 Update model binder to support editable list root objects
- #900 Add CslaModelBinder for IBusinessBase types
- #908 Add ScaffoldColumn and NotMapped attributes so scaffolding works with BusinessBase and BusinessListBase types
Xamarin
- #903 Fix the GraphMerger so it works on iOS devices - Find child type on iOS when indexer is not found
- #886 Upgrade to Xamarin Forms 3.0
- #886 Upgrade to Xamarin Forms 3.0 (also consolidate all json.net references to the same version)
- #697 Add Tag property to PropertyInfo class.
Blazor
- #829 Make UseTextSerialization property static
- #829 Remove MobileList test with complex types (breaking change - scenario no longer supported)
- #829 Add UseReflectionFallback setting to prevent use of System.Linq.Expressions
- #829 Make HttpProxy and HttpPortalController support optional text serialization
- #829 Expose GetValueOrNull method as public
- #829 Remove DCS dependency in MobileList
Bug fixes
- #897 Get BeginEdit working in netstandard 2.0 implementation
- Closes #545 Unhook event handlers before save operations.
- Closes #205 Call OnRefreshing before each OnRefreshed call.
- Fixes #761 Resolve exception when calling BeginRefresh
- Fix threading issue in InitializePerTypeRules (#614)
- Fix threading issue in InitializePerTypeRules (#614)
Misc
- #879 Update tests to work in .NET Core.
- #879 Add basic .NET Core undoable tests
- Closes #633 Closes #657 Closes #697 Add CustomTag property and fix null ref exception during control init. Make UpdateState public.
- Complete pt resources.Add some fr resources. (#884)
- Add ReadOnlyBase support for property setter anlyzer
- Mention contributor agreement in the getting started list
- #836 Make ConnectionManager types match; Optimize locking in DeRef method
Samples
- Add Wisej Web UI to ProjectTracker sample (#881)
- Update Project Tracker to 4.7.200-R18051402 ( #879))
- #829 Add BlazorExample sample code
- Remove useless overload RoleEdit GetRole(int id) (#687)
- ProjectTracker.BusinessLibrary.Netstandard is missing a reference to ProjectTracker.Dal (#870)
- ProjectTracker WinForms - show validation errors on Save (#868)
- Fix for ProjectTracker WinForms RolesEdit is broken (#863) UI
- Missing Display attribute (#863)
- Fix for ProjectTracker WinForms RolesEdit is broken (#863)
- ProjectTracker BO: add missing RoleList.CacheList (#865)
- Revert to RoleList cache refresh (#861)
- Async RoleList cache refresh (#861)
- Consistent codig of ResourceEdit and ProjectEdit (#861 (#861)
- Improve Project Tracker WinForms (#861)
- Updating samples to 4.7.101 (#859)
- Update sample to CSLA .NET 4.7.101 (#844) Cosmetic changes on some forms.
- Update SimpleNTier (broken Wcf configuration) sample to CSLA .NET 4.7.101 #844
- Update Project Tracker sample to CSLA .NET 4.7.101 #844
- Update CslaMVC sample to CSLA .NET 4.7.101 #844
- Refresh generated code (#847)
- Add sample to verify NuGet versions (#841)
- #832 Change NuGet targets to lib/net461
Important notes
There continue to be two "families" of CSLA .NET packages in NuGet. One that supports full .NET and one that supports all other runtimes. The following work item is tracking when this is resolved (after Microsoft fixes a bug in full .NET):
- #822OnDeserialized attribute from NS2 causes runtime error in full .NET
In the meantime, the full .NET family (based on the CSLA-Core package) must be used for the following types of app:
- Windows Forms
- WPF
- ASP.NET (other than Core)
- Console apps (other than Core)
- Azure Functions
- Any other runtime hosted by full .NET 4.6.1+
The netstandard family (based on the CSLA-Core-NS package) must be used for the following types of app:
- Xamrin
- UWP
- .NET Core
- ASP.NET Core
- Blazor
- Any other runtime not hosted by full .NET 4.6.1+
What this means for you is that if your n-tier app is 100% full .NET or full netstandard then you can live within one of those families. BUT if your server is full .NET and your client is Xamarin (for example) then your business library assemblies need to be compiled twice: once for full .NET and once for netstandard.
The Samples\ProjectTracker app shows how this is done by using a Shared Project to contain the code, and two concrete class library projects that compile the code for full .NET and netstandard respectively.
Also included are changes from 4.7.100 and 4.7.101
Version 4.7.101 is a bugfix release over 4.7.100. Release notes for 4.7.100 are below.
Version 4.7.101
- #832 Change NuGet targets from net46 to net461
- #836 BUG: Fix non-generic ConnectionManager
- #834 BUG: Csla.Web.Mvc4.dll for .NET461 reports version 1.0.0.0
- #844 Update samples to CSLA .NET 4.7.101 (thanks to tfreitasleal)
Version 4.7.100
I am pleased to announce the release of CSLA .NET version 4.7.100 with full support for netstandard 2.0 and .NET Core 2.
The packages are now in NuGet. Once some final updates to the samples are complete and merged into master I'll create a formal release tag/page on GitHub.
This release also includes some other very exciting capabilities, including:
- #760 Add support for ASP.NET Core 2.0
- #759 Add support for EF Core (EntityFrameworkCore)
- #813 Major performance improvement when data binding to large object graphs thanks to keithdv
- #795 Add
Transactionalattribute back into netstandard 2.0 code - #800 Changes to configuration so it is possible to configure CSLA without any
web.configorapp.configfiles (such as in .NET Core, etc.) - #496 Support
ClaimsPrincipalvia newCslaClaimsPrincipaltype - #729
ApplicationContextnow defaults to usingAsyncLocalto maintain values on the current thread/context with help from j055 BREAKING CHANGE - #712 Support in-place deserialization of an object graph
- #748 Major improvements to serialization via
MobileFormatterthanks to jasonbock - #763 Update to samples thanks to tfreitasleal
- #688 Get
ApplicationContext.Userauthentication working with ASP.NET Core thanks to dazinator - #766 Update to use latest UWP libraries for Windows 10 Fall Creators Update BREAKING CHANGE
- #790 ...
Version 4.6.603
Bug fixes from 4.6.600.
- #745 SerializationInfo.GetValue: _bindingEdit" error - UWP
- #744 Issue with Serializable, SerializableAttribute UWP
- #742 Problem with UWP's SerializationInfo
- #739 WcfProxy consistently uses DefaultBinding if enabled
- #735 Fix missing resources in netstandard 1.6
- #737 Fix serializable attribute issue in UWP BREAKING CHANGE (workaround)
🛑 🔐 Security warning: This version of CSLA .NET allows the use of
WcfProxy.WcfProxyuses 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 usingWcfProxyor upgrade to CSLA 6 or higher where this issue does not exist.
Version 4.6.600 release information:
This release is focused primarily on supporting .NET Core and NetStandard 1.6. There are also a number of bug fixes, enhancements, and improvements to some samples.
This release is available via NuGet.
CSLA .NET v4.6.500 supports the following platforms:
- .NET 4.0, 4.5, 4.6
- .NET Core via netstandard1.5 and netstandard1.6
- Xamarin iOS
- Xamarin Android
- Xamarin PCL (Profile111)
- UWP
Change highlights:
- #733 Remove WinRT packages from NuGet - CSLA no longer supports Win8 development as of version 4.6.600 BREAKING CHANGE
- #722 Add support for ASP.NET Core
- #708 Csla.AspNetCore.Mvc implementation
- #725 Update samples
- #701 Windows Forms now stores
Csla.ApplicationContext.Userin astaticfield instead of per-thread BREAKING CHANGE - Provide More Information in UndoException #472 (#718) BREAKING CHANGE
- RegisterProperty overload (propertyLambdaExpression
- Fix wrong role name in ProjectTracker Sample MockDb (#715)
- Mark SingleCriteria as obsolete #656 (#716)
- Update NuGet targets/dependencies (#713)
- #707 Add editorconfig file for solution (#714)
- #691 Update for VS 2017 (#706) BREAKING CHANGE FOR FRAMEWORK DEVS
- Samples/ProjectTracker Code fixes (#699)
- Fix PropertyConvert of nullable type to nullable enum property. #692 (#695)
- Fix DynamicBindingListBase constraint is missing Csla.Serialization.Mobile.IMobileObject #689 (#690)
- Delete Silverlight dependencies. (#685)
- Fix Sample ExtendableWcfPortalForDotNet (Rolodex) #678 (#683)
- CslaFastStart LastName update fix (#682)
- #680 Fixes trivia issue (#681)
- Allow SerializableAttribute on Enums (#672)
- Add fast start sample and readme (#670)
- Fixes #664 - Add logic to also ConvertFrom TypeConverter inside CoerceValue (#665)
- Throwing exception when sync dataportal tries to call async method on client (#643)