I do like how #copilot picks up the English language around #cslanet - like metastate properties and other CSLA jargon. I suppose this is because CSLA has been #oss for 28 years and Copilot was trained on open-source code (including CSLA).

We are pleased to announce the CSLA .NET version 9.1.0 release. This release includes enhancements and bug fixes from version 9.0.0.

https://github.com/MarimerLLC/csla/releases/tag/v9.1.0

#cslanet #dotnet

#cslanet version 9.1.0 beta is now online

https://github.com/MarimerLLC/csla/discussions/4675

#dotnet #blazor

#cslanet on Microsoft Learn

Using #cslanet with #blazor

https://learn.microsoft.com/en-us/shows/visual-studio-toolbox/using-csla-with-blazor

Some #cslanet #dotnet history

https://blog.lhotka.net/2025/04/21/CSLA-2-tier-Data-Portal-Behavior-History

Just merged what may be the largest PR in #cslanet history - Stephan added NRT support throughout much of the codebase!

Obviously this is a breaking change, and so will be part of version 10.

It is also a big improvement to the code.

We've pushed #cslanet version 7.0.7. Normally v7 would be too old for such a thing, but it is the last version that supports #xamarin and a community member submitted a fix to an issue that was blocking them from working, so it seemed wise to do the update.

We're very excited to share that #cslanet version 9.0.0 is now available!

This is a very big release, though with limited breaking changes. Tons of enhancements, improvements, optimizations, and bug fixes. And the most contributors of any release to date.

https://github.com/MarimerLLC/csla/blob/main/docs/Upgrading%20to%20CSLA%209.md

#dotnet #blazor #aspnetcore #azure #dotnetmaui

#cslanet version 8.2.9 is now online in nuget.

This version fixes an issue with Blazor state management.

https://github.com/MarimerLLC/csla/releases/tag/v8.2.9

#cslanet 9 release candidate 3 is now online.

https://github.com/MarimerLLC/csla/discussions/4427

So close to a #cslanet v9 release - except it turns out that the #dotnet #aot stuff required by #dotnetmaui now has quite the cascade effect in the code, so we're working through those issues before releasing 9.0. Some of the fixes may require subtle breaking changes.

I am sometimes reminded just how great it is to work on #oss projects like #cslanet and #kidsidkit.

People occasionally submit PRs out of the blue to fix bugs or backport massive changes to a previous version because they can't upgrade and need a feature.

So cool, and I am so happy!

#cslanet version 8.2.8 is now available in NuGet.

This is a bug fix release to address some issues with the previous release.

https://github.com/MarimerLLC/csla/discussions/4404

The CSLA 9 release candidate 1 is now on NuGet.

Details here: https://github.com/MarimerLLC/csla/discussions/4383

#dotnet #blazor #aspnetcore #dotnetmaui #cslanet

Then there's the issue of decoupling my (numerous) projects during release so the MAUI package (for example) can sync to MAUI releases, while the primary #cslanet package iterates much more frequently. I use project references today, sounds like my dev env is about to get more complex.

Given that #dotnetmaui 8 will go out of support in May 2025, months before #dotnet 8 itself, we need a strategy for dropping #cslanet satellite packages in a clean way.

I am looking for input on a good strategy.

Versioning strategy for UI packages · MarimerLLC/csla · Discussion #4349
https://github.com/MarimerLLC/csla/discussions/4349

A code-complete preview of #cslanet version 9 is now online in nuget.

Working to finalize CSLA 9 and expect it to release sometime in the next couple weeks.

We are in the final stretch of #cslanet version 9 - finalizing a few things and updating the samples and packaging.

Really looking forward to getting it out and available to everyone shortly after #dotnet 9 becomes available.

https://github.com/orgs/MarimerLLC/projects/17/views/1

#cslanet on #blazor from Microsoft Learn with @rockylhotka

https://learn.microsoft.com/en-us/shows/visual-studio-toolbox/using-csla-with-blazor

@Kissaki @SmartmanApps More accurately, #netstandard is the bridge between #netfx and #dotnet. It was a cross-platform thing when #xamarin and #uwp were viable, but today it is really just a migration bridge.

We use it a lot in #cslanet for example, because we support everything from #netfx 4.6.2 onwards.

For most mainstream developers though, this is all just background noise.