rijwanansari/CleanArchitectureDotNet7BlazorServer
43.9
Weak · 8 November 2026
859
lines of production code
C#
primary language
7
measurements over time
What this system is
This is a .NET 7 Blazor Server application designed to manage application settings and reference data. It provides a web interface for creating, reading, updating, and deleting configuration key-value pairs and reference fields. The system implements a layered architecture with a generic repository pattern to handle data persistence via Entity Framework Core.
Features
Added domain models for application settings and reference fields
The domain layer now includes new entities for managing application settings and reference data. Specifically, the \AppSetting\ class stores key-value pairs with metadata (reference key, value, description, and type), while \ReferenceField\ stores title and reference type information. Both entities inherit from new base classes (\AuditableWithBaseEntity\ and \BaseEntity\) that provide common auditing fields such as creation/modification dates and author/editor tracking, enabling consistent audit trails for these master data types.
Domain · high confidence
Initial WebApp scaffold with Blazor Server and App Setting management
The WebApp project has been initialized with a complete Blazor Server application structure, including the main router, layout components (MainLayout, EmptyLayout), and navigation menu. This update introduces a new App Setting management page that allows users to view, create, edit, and delete application settings through a dedicated interface. Additionally, the app now includes a Weather Forecast page that demonstrates data fetching from a service, alongside standard pages for Counter, Error handling, and unauthorized access scenarios.
WebApp · high confidence
Initial database schema and persistence infrastructure
The application now includes the initial Entity Framework Core migrations to create the 'AppSetting' and 'ReferenceField' database tables, along with the corresponding configuration classes and a generic repository implementation. This adds the foundational data access layer, including a unit-of-work pattern and dependency injection setup for the SQL Server database.
Infrastructure · high confidence
Introduce application-layer infrastructure for managing app settings
Added a new set of interfaces and models in the Application layer to support a generic repository pattern and unit-of-work abstraction. This includes the IAppSettingService and its implementation AppSettingService, which handle CRUD operations for AppSetting and ReferenceField entities. The change also introduces supporting infrastructure such as the ResponseModel for standardized API responses, AutoMapper profiles for DTO mapping, and dependency injection registration for the new services.
Application · high confidence
Behavioural changes
Project renamed and initialized with documentation and licensing
The solution file was renamed to reflect the new project name, and the repository was initialized with essential documentation and legal files. A comprehensive README.md was added, detailing the tech stack (.NET 7, Blazor Server, Entity Framework Core) and contribution guidelines. Additionally, a LICENSE.txt file was added to specify the MIT License, and a .gitignore file was updated to include build artifacts and user-specific files, while the previous .gitattributes configuration was removed.
(repo-wide) · high confidence
Dependencies
Migrate to .NET 7 and update core libraries
The project has been upgraded to .NET 7 across all layers (Application, Domain, Infrastructure, and WebApp). This includes updating the target framework and aligning key dependencies such as Entity Framework Core 7.0.0, AutoMapper 12.0.0, and Newtonsoft.Json 13.0.2. These changes ensure compatibility with the latest .NET runtime and provide access to new features and performance improvements.
(dependencies) · high confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 42 → 44 (+1.4)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 60 → 60 (+0.0)
- Architecture 84 → 84 (+0.0)
- Maturity 47 → 53 (+5.4)
- Readiness 47 → 51 (+3.8)
- Security 33 → 33 (+0.8)
- Accessibility 47 → 47 (+0.6)
- Performance 100 → 100 (+0.0)
Resolved (3)
- End-of-life runtime: .NET net7.0 (WebApp/WebApp.csproj)
- The interface IRepository<T> defines a method Delete taking an expression, while the implementation EfRepository<T> also defines Delete taking an expression. However, EfRepository<T> also defines DeleteAsync(object) and DeleteAsync(object, T) is not present but UpdateAsync is. More critically, looking at IRepository<T>, it has Delete(Expression) and Update(T). EfRepository<T> has Delete(Expression), DeleteAsync(object), DeleteAsync(Expression), Update(T), UpdateAsync(object, T). The naming is consistent between interface and implementation for the primary operations. However, there is a potential inconsistency in the IRepositoryService<T> vs IRepository<T> naming for similar concepts. IRepository<T> has Get, GetMany, AddAsync, Update, Delete. IRepositoryService<T> has GetAsync, GetByIdAsync, UpsertAsync, DeleteAsync. The service layer uses Async suffixes for all async methods, while the repository interface mixes Async (AddAsync) and non-async names for async operations (Get, GetMany, Delete, Update). This is a common pattern but technically an inconsistency in verb usage across the same conceptual layer of data access.
- Vulnerable: AutoMapper
New (4)
- End-of-life runtime: .NET net7.0 (Application/Application.csproj)
- End-of-life runtime: .NET net7.0 (Domain/Domain.csproj)
- End-of-life runtime: .NET net7.0 (Infrastructure/Infrastructure.csproj)
- End-of-life runtime: .NET net7.0 (WebApp/WebApp.csproj)
Architecture
- Unchanged — 2 containers · 1 contexts · 0 edges
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
rijwanansari/CleanArchitectureDotNet7BlazorServer was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 8 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit c425519083c2733c0917a27e60f7dba31d232892 — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-45ab2cab63de.