How ramenofficialgovpatsy/floors-manufacturing-system works
Project type and purpose
• This is a full-stack, cross-platform desktop application (“Floors Manufacturing Management System”) built with Avalonia UI (.NET/C#) using the MVVM pattern.
• It automates CRM, product catalog, order processing (with progressive discounts), warehouse inventory, and a multi-stage workflow.
File structure
• Top-level artifacts
• Program.cs, App.axaml(.cs), MainWindow.axaml(.cs): application and startup
• Master_Floor_Project.sln / .csproj: solution and project files
• Data/AppDbContext.cs: EF Core DbContext
• Models/: domain entities
• Services/: business logic and abstractions
• ViewModels/: presentation logic
• Views/ & Windows/: XAML UI definitions
• Converters/: UI value converters
• Assets/: images, resources
• Architectural hints
• MVVM layers (Views ↔ ViewModels ↔ Models + Services)
• Dependency Injection is used (I*Service interfaces)
• EventAggregator for event-driven module communication
• Entity Framework Core + Npgsql talking to PostgreSQL
README for additional insights
• Confirms technology stack: Avalonia UI (frontend), .NET 9.0/C# 11 (backend), EF Core, PostgreSQL
• Architectural patterns: MVVM, DI, event-driven communication
a. Main components
1. Client/UI Layer
• Views & Windows (XAML)
• Converters
2. Presentation Layer
• ViewModels
• NavigationService & EventAggregator
3. Domain/Business Layer
• Services (ApplicationService, ProductService, DiscountService, PartnerService, WarehouseService)
• Service Interfaces (IApplicationService, etc.)
4. Data Access Layer
• AppDbContext (EF Core)
• Models/entities
5. Database
• PostgreSQL (hosted externally or locally)
6. External Libraries/Frameworks
• Avalonia UI, CommunityToolkit.MVVM, EF Core, Npgsql
b. Relationships & interactions
• UI binds to ViewModels (two-way data binding)
• ViewModels call Services via injected interfaces
• Services orchestrate business logic and use DbContext to query/update Models
• DbContext uses EF Core + Npgsql to communicate with PostgreSQL
• EventAggregator publishes/subscribes events among ViewModels/Services
• NavigationService orchestrates view/window transitions
c. Architectural patterns/design principles
• MVVM: separation of UI (Views) and presentation logic (ViewModels)
• Dependency Injection: ViewModels depend on I*Service abstractions, resolved at startup
• Repository-style Data Access via EF Core
• Event-driven communication for decoupling
d. Key technologies/frameworks
• Avalonia UI for cross-platform desktop UI
• XAML for layout + Converters
• CommunityToolkit.MVVM for INotifyPropertyChanged, RelayCommands
• EF Core (AppDbContext) and Npgsql for ORM and DB connectivity
• PostgreSQL as the relational database