JJ.Framework.Business.Legacy 0.260.7438

JJ.Framework.Business.Legacy

Classes to support a business logic layer.

A historic version released in aid of older apps, that still hold value. Now targets .NET 10 and .NET Standard supporting native compilation and code trimming for wide compatibility, with 100% meaningful test coverage, doc pop-ups everywhere.

A version from a different point in time is JJ.Framework.Business. That one has additional classes to manage bidirectional relationships between entities, but also excludes the EntityStatusManager class. It only officially supports an older version of .NET, even though compatibility with a newer .NET should be fine.

• Result types - Elegant way to return data, status and messages from your operations.

  • IResult - Common interface for result types.
  • ResultBase - Base class with core properties: Success and Messages.
  • Result - Use when there's no return value, just success / failure info.
  • Result<T> - Returns data along with the status metadata.

• EntityStatusManager

  • Simple in-memory holder for entity/storage state like New, Dirty and Deleted.
  • The goal: let business logic ask "does this object look new/dirty/deleted? without depending on a database or a large persistence framework. You can fill this object from wherever is convenient (service code, UI, or persistence layer) and pass it around. Business rules can then react to those flags (for example: update LastModified) without being tied to how the data is stored.

• ISideEffect

  • Used for some polymorphism between small pieces of business logic that go off as a result of altering or creating data. For instance storing the date time modified or setting default values or automatically generating a name might all be wrapped in side-effects, that are executed upon calling methods, like Create, Update and Delete. Using separate classes for side-effects, creates overview over those pieces of business logic, that are the most creative of all, and prevents those special things that need to happen from being entangled with other code.

• GetListIsDirty

  • Compares two lists (a source list of data and a destination list of data). Determines whether a list is dirty. This means that it checks whether items were removed, added or changed. (The changing of items does not mean that the entities themselves are dirty, it means that a list position now points to another object.)

Release Notes

2026-02-23 | 0.250/3.8 : Legacy

• Historic version. Full meaningful test coverage. Features:
• EntityStatusManager and GetListIsDirty:
• Framework-agnostic New/Deleted/Dirty flag container.
• ISideEffect for keeping business logic units separated.
• Bug fix: Entity status New and Deleted were accidentally stored as Dirty.

2026-07-07 | 0.258/5.0 : Result Type Legacy Move

• Result types.
• Moved from .Core to the .Legacy project.
• Removed JJ.Business.IO.Core project variant.
• Full, meaningful test coverage, IntelliSense docs.
• Tighter nullability, diagnostic texts.

2026-07-08 | 0.259/5.1 : Result Type Rework

• Success = false by default (previously true) improving compatibility and security.
• Add Succesful and VoidResult aliases for Success and Result for compatibility.
• Messages not separated by commas in diagnostics texts. Punctuation left up to the messages themselves.

💬 Feedback

Got feedback or questions? You can reach me here.