lionfire-core

LionFire.Core Repository

Ambitious set of mini-frameworks being developed for other LionFire packages, mostly targeting .NET 9.0+ (with some deprecated parts in .NET Framework 4.8 and netstandard2.0).

External Docs: https://lionfire.readthedocs.io (older) Home: https://open.lionfire.software

---

📚 Documentation

Comprehensive documentation is now available! Over 20,000 lines covering async data access, MVVM patterns, Blazor UI components, workspace architecture, and more.

🚀 Quick Start Guides

Choose your path based on what you're building:

• Blazor UI Development ⭐ Building reactive Blazor apps (START HERE for UI)
• Async Data Access - IGetter, ISetter, IValue patterns for async operations
• MVVM Patterns - ViewModels, reactive binding, and data integration
• Workspace System - User-centric multi-workspace applications

📖 Documentation Areas

Domain Documentation (Cross-library guides and tutorials):

• MVVM Domain - Complete MVVM guide (5,053 lines, 6 docs)
• Async Data Domain - Data access patterns (3,882 lines, 6 docs)
• UI/Blazor Domain - Blazor component patterns (2,769 lines, 4 docs)
• VOS Domain - Virtual Object System reference
• Workspace Domain - Workspace system guide

Architecture Documentation (System design and layer relationships):

• Core Architecture - Repository design philosophy and layers
• MVVM Architecture - MVVM system design (5 docs)
• Async Data Architecture - Data access architecture (4 docs)
• Workspace Architecture - Workspace system design (4 docs)
• Reactive Architecture - Reactive patterns (in progress)

Library Reference (Per-library technical docs):

• See individual CLAUDE.md files in src/*/CLAUDE.md

📋 Complete Documentation Index

📖 docs/README.md - Full documentation navigation, examples, and library index

🎯 Common Tasks

• Building a Blazor workspace app? → Create Blazor Workspace Page
• Need to understand data access? → Async Data Overview → Getters & Setters
• Working with ViewModels? → MVVM Overview → ViewModels Guide
• Want the big picture? → Architecture Overview → Layers Guide

---

Status

This is only really intended to be usable to me, but feel free to mine the codebase for interesting parts, and let me know if you think the community would benefit from anything being a properly published and supported OSS project. I intend to do this for several packages, but I am not in a rush at the moment.

Roadmap

I am fleshing all this out for my own purposes as I need to and am inclined to, with the goal of creating components and frameworks that are useful in the long term. While I intend for the frameworks and libraries to be decoupled, they may share some common interfaces that hopefully raise the lowest common denominator from the BCL, making some patterns possible that I intend to use heavily, such as multi-typing.

If you find a certain part interesting and want to help advance it into a first class library or framework, let me know.

Philosophy

• Base layer
  • Minimal dependencies
• Core Toolkit
  • provides some innovative cross-cutting functionality
  • mostly unopinionated
• Toolkits
  • unopinionated
  • the bulk of complex innovation
  • may depend on each other
  • Intended to be a la carte: some toolkits will die, some will live on. They are kept separate so this can happen organically. Though some of them form a deep stack for data persistence.
• The LionFire Framework
  • An opinionated holistic framework that integrates several LionFire Toolkits, by default
  • the idea: dotnet new lionfire-app to get a new Program.cs with the boatload of features I want for every app from one line of code: new HostApplicationBuilder().LionFire();

Outline of Available Libraries

See also

First, here are projects that have been spun off into their own repo:

State Machines

• Class State Machine generator

Trading

• Trading related code (crypto, forex, bots, etc.)

Base layer

LionFire.Base

• no dependencies
• Augments .NET's BCL

LionFire.Flex