Bee.Api.Core
4.2.0
dotnet add package Bee.Api.Core --version 4.2.0
NuGet\Install-Package Bee.Api.Core -Version 4.2.0
<PackageReference Include="Bee.Api.Core" Version="4.2.0" />
<PackageVersion Include="Bee.Api.Core" Version="4.2.0" />
<PackageReference Include="Bee.Api.Core" />
paket add Bee.Api.Core --version 4.2.0
#r "nuget: Bee.Api.Core, 4.2.0"
#:package Bee.Api.Core@4.2.0
#addin nuget:?package=Bee.Api.Core&version=4.2.0
#tool nuget:?package=Bee.Api.Core&version=4.2.0
Bee.NET Framework
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:
FormSchemaserves 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.0for modern .NET runtime support. - 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. |
| 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.Api.AspNetCore.dll | JSON-RPC 2.0 API controller for ASP.NET Core; unified endpoint for backend method dispatch. |
Frontend
| Assembly Name | Description |
|---|---|
| Bee.Api.Client.dll | Connector for local or remote invocation of backend Business Objects. |
💡 Sample Project
Refer to bee-jsonrpc-sample, which includes examples of JSON-RPC server and client implementations, and demonstrates how to use the Connector for both local and remote connections.
📬 Contact & Follow
You're welcome to follow my technical notes and hands-on experience sharing
| Product | Versions 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. |
-
net10.0
- Bee.Api.Contracts (>= 4.2.0)
- Bee.Definition (>= 4.2.0)
NuGet packages (4)
Showing the top 4 NuGet packages that depend on Bee.Api.Core:
| Package | Downloads |
|---|---|
|
Bee.Connect
Connector for local or remote invocation of backend logic. |
|
|
Bee.Api.AspNetCore
Provides a JSON-RPC 2.0 API controller for ASP.NET Core, serving as a unified endpoint to handle backend method calls via JSON-RPC protocol. |
|
|
Bee.Api.AspNet
Provides a JSON-RPC 2.0 API HttpModule for ASP.NET, enabling a unified HTTP POST endpoint for invoking backend methods via the JSON-RPC protocol. |
|
|
Bee.Api.Client
Connector for local or remote invocation of backend logic. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 4.2.0 | 0 | 5/13/2026 |
| 4.1.0 | 116 | 5/5/2026 |
| 4.0.2 | 115 | 4/23/2026 |
| 4.0.1 | 218 | 4/9/2026 |
| 4.0.0 | 152 | 4/9/2026 |
| 3.6.2 | 352 | 11/7/2025 |
| 3.6.1 | 315 | 10/28/2025 |
| 3.6.0 | 263 | 10/24/2025 |
| 3.5.2 | 317 | 10/15/2025 |
| 3.5.1 | 285 | 10/5/2025 |
| 3.5.0 | 302 | 9/25/2025 |
| 3.4.9 | 298 | 9/25/2025 |
| 3.4.8 | 276 | 9/24/2025 |
| 3.4.7 | 288 | 9/23/2025 |
| 3.4.6 | 323 | 9/22/2025 |
| 3.4.5 | 333 | 9/22/2025 |
| 3.4.4 | 325 | 9/22/2025 |
| 3.4.3 | 275 | 9/21/2025 |
| 3.4.2 | 407 | 9/18/2025 |
| 3.4.1 | 403 | 9/16/2025 |