3.2 KiB

Raw Blame History

Architecture

Solution Dependency Graph

FruitBank.Common (shared domain, net9.0)
    ↑
FruitBank.Common.Server (server-side services, nopCommerce, net9.0)
    ↑
FruitBankHybrid.Shared.Common (shared utilities, net10.0)
    ↑
FruitBankHybrid.Shared (Blazor UI components, pages, services, net10.0)
    ↑                ↑                      ↑
FruitBankHybrid    FruitBankHybrid.Web    FruitBankHybrid.Web.Client
(MAUI, net10.0)    (Server, net10.0)      (WASM, net10.0)

All projects also reference AyCode.Core (net9.0) and AyCode.Blazor (net10.0) via DLL references (not ProjectReference).

Target Frameworks

nopCommerce 4.80.9 requires .NET 9

Project	TFM	Reason
FruitBank.Common	net9.0	nopCommerce entity references
FruitBank.Common.Server	net9.0	nopCommerce server integration
FruitBankHybrid.Shared	net10.0	Blazor UI
FruitBankHybrid.Shared.Common	net10.0	Shared utilities
FruitBankHybrid	net10.0‑android/ios/win	MAUI Hybrid
FruitBankHybrid.Web	net10.0	Blazor Server host
FruitBankHybrid.Web.Client	net10.0	Blazor WASM
FruitBankHybrid.Shared.Tests	net10.0	Tests
AyCode.Core (external)	net9.0	Foundation — used by nopCommerce layer
AyCode.Blazor (external)	net10.0	UI framework
AyCode.Core.Serializers.SourceGenerator	netstandard2.0	Roslyn analyzer requirement

Three Deployment Targets

Target	Project	How UI Runs
MAUI Hybrid	FruitBankHybrid	Native app with BlazorWebView
Blazor Server	FruitBankHybrid.Web	Server-side rendering + SignalR
Blazor WASM	FruitBankHybrid.Web.Client	Downloaded to browser, runs in WASM

All three share the same UI components from FruitBankHybrid.Shared.

Data Flow

User → DevExpress Grid → AcSignalRDataSource → SignalR (AcBinary) → DevAdminSignalRHub
                                                                          ↓
                                                                    DynamicMethodRegistry
                                                                          ↓
                                                          IFruitBankDataControllerServer
                                                          ICustomOrderSignalREndpointServer
                                                          IStockSignalREndpointServer
                                                                          ↓
                                                                  nopCommerce Database

Key Architectural Decisions

nopCommerce plugin — Customer, Order, Product are nopCommerce entities extended via GenericAttributes and DTOs
SignalR over REST — all data flows through SignalR with AcBinary protocol
DevExpress Blazor 25.1.3 — exclusive UI component library
Three measurement hierarchies — Shipping/Order/StockTaking share same base but have different audit rules
Client-side database — DatabaseClient caches entities in ConcurrentDictionary for offline/fast access
Platform-specific credential storage — MAUI uses SecureStorage, Web uses obfuscated localStorage, Server uses no-op

3.2 KiB Raw Blame History Unescape Escape