Bee.Repository 4.5.0

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher. 
dotnet add package Bee.Repository --version 4.5.0
                    


                    

                
NuGet\Install-Package Bee.Repository -Version 4.5.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="Bee.Repository" Version="4.5.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="Bee.Repository" Version="4.5.0" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Bee.Repository" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add Bee.Repository --version 4.5.0
                    


                    

                
#r "nuget: Bee.Repository, 4.5.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package Bee.Repository@4.5.0
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=Bee.Repository&version=4.5.0
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Bee.Repository&version=4.5.0
                    


                            Install as a Cake Tool

Bee.NET Framework

繁體中文

Quality Gate Status Bugs Vulnerabilities Code Smells Coverage

Bee.NET Framework is an N-Tier + Clean Architecture + MVVM hybrid designed to accelerate the development of enterprise information systems. It adopts a Definition-Driven Architecture, using FormSchema as the single source of truth to drive UI layout, database schema, and business validation in a unified way.

📌 N-tier means the architecture is divided into more than three logical layers. In Bee.NET, the system is separated into at least five layers: presentation, API communication, business logic, data access, and database — each with a clearly defined responsibility.

All packages target net10.0.

✨ Features

  • Definition-Driven Architecture: FormSchema serves as the single source of truth, automatically deriving UI layout (FormLayout), database schema (TableSchema), and validation rules — define once, sync everywhere.
  • N-Tier + Clean Architecture + MVVM: Clear separation of presentation, API, business logic (BO), and data access layers, borrowing the best concepts from each pattern for ERP scenarios.
  • Cross-platform compatibility: All packages target net10.0 for modern .NET runtime support.
  • Multi-database support: Built-in dialects for SQL Server, PostgreSQL, SQLite, MySQL, and Oracle; host applications register only what they use.
  • Modular components: Decoupled libraries for core utilities, data, caching, business logic, and API hosting.
  • Rapid development: Reusable base classes and FormSchema-driven CRUD reduce repetitive boilerplate.

📐 Architecture

For an in-depth look at the layered architecture, data flow, and design decisions behind Bee.NET, see the Architecture Overview.

For guidelines on API Contract and BO Parameter design (Request/Response vs Args/Result), see the API/BO Contract Design Principles.

For the full developer documentation index, see docs/README.md.

📦 Assembly

Shared (Frontend / Backend)

Assembly Name Description
Bee.Base.dll Core utilities such as serialization, encryption, and general-purpose helpers.
Bee.Definition.dll Defines system-wide structured types including FormSchema, field schemas, and layout configurations.
Bee.Api.Contracts.dll Shared data contracts (request/response models) used by both frontend and backend.
Bee.Api.Core.dll Encapsulates API support such as model definitions, payload encryption, and serialization pipeline.

Backend

Assembly Name Description
Bee.Repository.Abstractions.dll Interface contracts for the business layer to access the data layer; boundary between Business Object and Repository.
Bee.ObjectCaching.dll Runtime caching of FormSchema definitions and derived system data to improve performance.
Bee.Db.dll Database abstraction with dynamic SQL command generation and connection binding; ships dialects for SQL Server, PostgreSQL, SQLite, MySQL, and Oracle.
Bee.Repository.dll Common repository base classes and FormSchema-driven data access mechanisms.
Bee.Business.dll Core business logic (Business Object / BO) implementing use-case workflows.
Bee.Hosting.dll Composition root — AddBeeFramework extension registering all backend services into any IServiceCollection (no ASP.NET Core dependency). Used by ASP.NET Core, WinForms, Console, and Worker Service hosts.
Bee.Api.AspNetCore.dll JSON-RPC 2.0 API controller for ASP.NET Core (UseBeeFramework middleware + ApiServiceController).

Frontend

Assembly Name Description
Bee.Api.Client.dll Connector for local or remote invocation of backend Business Objects (LocalApiProvider / RemoteApiProvider).
Bee.UI.Core.dll Cross-platform UI common layer (ClientInfo / IEndpointStorage / IUIViewService / VersionInfo); shared by native UI hosts for client-side connection state and endpoint persistence.
Bee.UI.Maui.dll MAUI cross-platform control library (iOS / Android / macOS / Windows); ships FormSchema-driven controls (DynamicForm + FormDataObject). Default TFM net10.0; platform TFMs opt-in via -p:BeeUiMauiFullPlatforms=true.
Bee.Web.Blazor.Server.dll Razor Class Library (RCL) for Blazor Server hosts; provides DI-scoped connectors and Blazor components (DynamicForm, FormDataObject).
Bee.Web.Blazor.Wasm.dll Razor Class Library (RCL) for Blazor WebAssembly hosts; forced to RemoteApiProvider. Must not depend on any backend project.

🚀 Quick Start

Want to see Bee.NET running in 30 seconds?

# Terminal 1 — start the JSON-RPC API host
cd samples/QuickStart.Server
dotnet run

# Terminal 2 — connect and call the Echo BO
cd samples/QuickStart.Console
dotnet run

The console will print System.Ping status and an echoed message returned from a custom BO. See samples/README.md for the full demo list and what each one shows.

💡 Sample Projects

  • In-repo demos under samples/ — minimal, focused, shipped alongside the framework. Built with dotnet build samples/Bee.Samples.slnx (independent of the main Bee.Library.slnx, so the main CI/build stays unaffected).
  • bee-jsonrpc-sample — earlier external sample that shows JSON-RPC server / client implementations and Local / Remote connector usage.

📬 Contact & Follow

You're welcome to follow my technical notes and hands-on experience sharing

Facebook ｜ HackMD ｜ GitHub ｜ NuGet

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on Bee.Repository:

Package Downloads
Bee.Hosting

Composition root for the Bee.NET framework. Registers backend services into any IServiceCollection — usable from ASP.NET Core, WinForms/WPF, Console, Worker Service, and integration test hosts without pulling in ASP.NET Core.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
4.5.0 0 5/23/2026
4.4.0 108 5/16/2026
4.3.0 110 5/13/2026
4.2.0 99 5/13/2026
4.1.0 98 5/5/2026
4.0.2 102 4/23/2026
4.0.1 120 4/9/2026
4.0.0 108 4/9/2026
3.6.2 249 11/7/2025
3.6.1 224 10/28/2025
3.6.0 182 10/24/2025