How israel-bsi/realtyhub works
Project type and purpose
• This is a full-stack .NET real-estate management system (“RealtyHub”) built as a Blazor WebAssembly application with a separate Web API service and a shared domain library.
• Purpose: allow users to manage properties, viewings, offers, contracts, customers, condominiums and generate reports; authenticate users; send emails; store contract templates and generated documents.
File structure
• Top-level solution: RealtyHub.sln
• RealtyHub.Core
• Shared domain models, DTOs (Requests/Responses), enums, handler interfaces, utilities (fake data), service abstractions (IEmailService, ISearchCep).
• RealtyHub.ApiService
• Minimal-API endpoints (Endpoints/… .cs), handlers (business logic), EF Core DbContext + entity mappings, migrations, services (EmailService, ContractGenerator, ReportServices), configuration (appsettings, DI registrations), Program.cs.
• RealtyHub.AppHost
• ASP.NET Core host for the Blazor client (serves static files, configures proxy to the ApiService, authentication settings).
• RealtyHub.Web
• Blazor WebAssembly client: UI components, pages, layout, component handlers, client-side services (ViaCepService, EmailService, Report clients), security (cookie auth), wwwroot assets.
• RealtyHub.Tests
• Unit and integration tests for core handlers and API endpoints.
Essential details
• Shared Core project as a “package” dependency of both Web and ApiService
• Critical flows: authentication (login → token or cookie → subsequent calls), email generation, report PDF generation
• Don’t over-complicate: focus on each distinct layer and its primary responsibilities