nikolagsiderov / APPartment

Home Management System, which is .NET-based. Blazor & MVC as web clients, consuming from a Web API. Services operating with a custom ORM framework, retrieving data from a SQL Server database.
3 stars 2 forks source link
api blazor blazor-server dotnet-core framework net5 object-relational-mapping orm-framework sql sql-server webapi

Project's development lifecycle:

At start, Entity Framework Core with code first approach was used, then I migrated to database first, later on EF Core was entirely removed and I developed my own custom object-relational mapping framework.

The project was also initially started with a MVC architecture, with all the business logic implemented in the controller levels. After which, a new Web API project was initialized with a proper business layer where the business logic was migrated. The MVC project send requests to the API and retrieved responses in the form of view-models to display in its views.

This was incomplete and the MVC architecture was redundant, having to support its controllers (only to make calls to the API). I implemented a new web client, under the hood of Blazor, using latest .NET 5. Now, the new web client was dynamic and was just that - a web client, nothing more.

What I have learned

Business description