Bot releases are hidden (Show)
Published by rockfordlhotka almost 4 years ago
The 5.4.0 release of CSLA .NET adds support for .NET 5 across all supported scenarios, including:
The release notes doc contains more details.
Published by rockfordlhotka about 5 years ago
I am pleased to announce the release of CSLA .NET version 4.11.2.
This is a bug fix release from 4.11.1.
I am pleased to announce the release of CSLA .NET version 4.11.1.
This is a bug fix release from 4.11.0.
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.
LocalProxy
would lock a Windows Forms app using async data portal callsUpdateAllChildren
method to FieldManager
to simplify saving all child objects regardless of their IsDirty
valueI am pleased to announce the release of CSLA .NET version 4.10.1.
This is a bug fix release from 4.10.0.
HttpProxy
to autoflush text writerI am pleased to announce the release of CSLA .NET version 4.10.0.
This is a bug fix release from 4.9.0.
The major enhancements are described in some detail in a CSLA .NET 4.9.0 blog post.
We've started using Dependabot to help keep NuGet dependencies current. As a result, the following updates are included in this release:
We've updated some of the docs and officially removed the wiki. All the wiki/docs content is now in the /docs directory.
SaveAndMergeAsync
methodsIsOffline
property for data portalIDataPortalFactory
singleton for page injection in ASP.NET CoreCsla.Configuration.CslaConfiguration
CslaConfigurationOptions
ConfigureCsla
extension method to IConfiguration
for use in .NET Core configurationAddCsla
method for use in ASP.NET Core ConfigureServices
You can see all the closed work items in GitHub.
Published by rockfordlhotka about 6 years ago
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:
From 4.8.0:
CSLA-Core-NS
package 🛑BinaryFormatter
in .NET Standard 2.0 and .NET CoreDisplayName
value so localization works as expected âš String.Empty
not null
âš NullReferenceException
in Rule.Complete
âš HttpProxy
/docs
directory so it is part of the repoYou 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.
Published by rockfordlhotka over 6 years ago
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.
This is a pretty big release, focused on four key areas:
CslaModelBinderProvider
and CslaModelBinder
types support data binding in Razor Pages scenariosPropertyInfo
type, Fixed critical bug in GraphMerger
on iOSCSLA-Core-NS
package from your Blazor client app to use CSLAMore details are listed here:
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):
In the meantime, the full .NET family (based on the CSLA-Core
package) must be used for the following types of app:
The netstandard family (based on the CSLA-Core-NS
package) must be used for the following types of app:
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.
Version 4.7.101 is a bugfix release over 4.7.100. Release notes for 4.7.100 are below.
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:
Transactional
attribute back into netstandard 2.0 codeweb.config
or app.config
files (such as in .NET Core, etc.)ClaimsPrincipal
via new CslaClaimsPrincipal
typeApplicationContext
now defaults to using AsyncLocal
to maintain values on the current thread/context with help from j055 BREAKING CHANGE
MobileFormatter
thanks to jasonbock
ApplicationContext.User
authentication working with ASP.NET Core thanks to dazinator
AmbiguousMatchException
in data portal thanks to iherwald
Save
method issue thanks to rabidkitten
There are a couple known issues with this release:
System.Data.SqlClient
show a warning about this assembly's locationwarning PRI263: 0xdef01051
messages relative to CSLA resource stringsRegarding the NuGet/assembly split noted in #822:
Right now there are two "families" of CSLA .NET packages in NuGet. One that supports full .NET and one that supports all other runtimes.
The full .NET family must be used for the following types of app:
The netstandard family must be used for the following types of app:
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.
Published by rockfordlhotka over 7 years ago
Bug fixes from 4.6.600.
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:
Change highlights:
Csla.ApplicationContext.User
in a static
field instead of per-thread BREAKING CHANGE
Published by rockfordlhotka about 8 years ago
The primary focus of this release is the addition of support for .NET Core 1.0. This was accomplished by adding a NetStandard 1.5 project to the solution, with the output being part of the CSLA-Core NuGet package.
CSLA .NET v4.6.500 supports the following platforms:
Here are the changelog highlights:
Published by rockfordlhotka over 8 years ago
This release is focused primarily on enhancing the existing Xamarin support. There is now a Csla.dll targeting PCL Profile111, which is the current profile for Xamarin.Forms projects and .NET Core.
There is also now a CSLA-Xamarin NuGet package that includes a Csla.Xaml.dll with support for Xamarin.Forms. This includes the same viewmodel base classes as the other XAML platforms, and an implementation of the PropertyInfo
control tailored for use in Xamarin.Forms.
@JasonBock added even more analyzers for Visual Studio 2015 to help developers avoid common coding mistakes when building CSLA .NET business classes.
We now have support for the prerelease of Entity Framework 7.
The pt and pt-BR resources for Csla.dll have been updated. Other languages need updates as well - please contribute if you are a native speaker!
There is a new way to customize the server-side data portal by implementing an interceptor that is invoked via the new DataPortalBroker
. (#564)
This release is available via NuGet.
You can see the change logs for the 4.6.x releases:
There are some important non-technical or semi-technical enhancements, including:
At a high level the technical enhancements include:
LazyGetProperty
and LazySetProperty
methods to simplify lazy loading of valuesSerialized
and other implementations in Xamarin and UWPHttpProxy
talking to an HttpPortal
endpointWhat was removed?
Published by rockfordlhotka over 8 years ago
Version 4.6.301 is a bug fix update to 4.6.300. It addresses the following:
The following is from the 4.6.300 release:
Note: As of this release CSLA .NET is now under the MIT open source license. If you want to continue using CSLA .NET under the previous license terms you must not upgrade to version 4.6.300.
The primary new feature in this release is support for Portable Class Libraries for the following target set:
Note: The PCL support in this version is generally unstable. You should upgrade to a newer release that has complete PCL support if you intend on referencing CSLA from a PCL.
There are also some new analyzers and numerous bug fixes. See the change log for more details.
You can see the change logs for the three 4.6.x releases:
There are some important non-technical or semi-technical enhancements, including:
At a high level the technical enhancements include:
LazyGetProperty
and LazySetProperty
methods to simplify lazy loading of valuesSerialized
and other implementations in Xamarin and UWPHttpProxy
talking to an HttpPortal
endpointWhat was removed?
Published by rockfordlhotka about 9 years ago
This is a bug-fix and minor update release over 4.5.700.
There are possible breaking changes due to updates to numerous NuGet package dependencies. You will need to update those dependent packages to use this newer version of CSLA 4.
Change log for this release.
Update to support the latest Xamarin capabilities, including the Unified API and updated iOS projects.
Also includes a number of bug fixes and minor enhancements. See the change log for details.
This release of CSLA .NET allows you to share your business code (normally unchanged) across the following platforms:
Published by rockfordlhotka about 10 years ago
The GitHub code is post-3.8.4. The binaries are the 3.8.4 release.
Version 3.8.4 supports:
Published by rockfordlhotka over 10 years ago
This is CSLA .NET version 4.3.14 with support for .NET 4, WP7, Silverlight 4, and Silverlight 5.
Published by rockfordlhotka over 10 years ago
This is CSLA .NET version 3.0.5 with support for .NET 2.0 and .NET 3.0.
Published by rockfordlhotka over 10 years ago
This is the version 1.53 release of CSLA .NET, targeting .NET 1.1.
More info is available at this location.