| name | vrt-resume |
| description | Work on the VRT.Resume .NET 10 ASP.NET Core MVC resume generator codebase. Use when editing VRT.Resume, adding features to this repo, fixing bugs here, running tests/build, deploying to Azure, or when the user mentions VRT.Resume, CV generator, or this solution. Always read AGENTS.md at repo root first.
|
VRT Resume Codebase
Before any work
- Read
AGENTS.md at the repository root — it is the canonical knowledge base.
- Identify affected layer: Domain → Persistence → Application → Mvc → Tests.
- Prefer existing patterns over new abstractions.
Quick context
- Stack: .NET 10, MediatR CQRS, FluentValidation, CSharpFunctionalExtensions
Result, EF Core (SQLite dev / SQL Server prod), OAuth cookie auth.
- Build:
dotnet build VRT.Resume.sln -c Release
- Test:
dotnet test VRT.Resume.sln -c Release (requires SQL Server LocalDB)
- Publish:
dotnet publish VRT.Resume.Mvc/VRT.Resume.Mvc.csproj -c Release -o ./deploy/web
Adding a feature (short path)
- Entity + EF config in Domain/Persistence (if new data).
- Command/Query + nested Handler + Validator in Application (
Persons/ or Resumes/).
- Reuse
UpsertHandlerBase / DeleteHandlerBase / HandlerBase when possible.
- Controller action in Mvc calling
Send().
- Razor view + resource strings in
VRT.Resume.Resources.
- Integration test in
VRT.Resume.Application.Tests.Unit/.
Critical rules
- Never
git push unless the user explicitly asks — commits OK when requested; user reviews before push.
- No repository layer — handlers use
AppDbContext directly.
- No EF migrations —
EnsureCreated() only; warn user on schema-breaking changes.
- Global auth —
[AllowAnonymous] required for public endpoints.
- Transient DbContext — do not change lifetime without explicit request.
- Central packages — versions in
Directory.Packages.props only.
- Tests are integration tests despite
Tests.Unit folder name.
- Language: documentation, code comments, and commit messages in English; UI strings via Resources (PL + EN).
- Adding a language: sync
SupportedLangDic / SupportedLanguages in both CultureService (Mvc) and PwaCultureService (Pwa), add LabelResource.{xx}.resx + MessageResource.{xx}.resx; PWA CultureSelector auto-scales — see AGENTS.md → Adding a new language.
VRT.Resume.Pwa
- Blazor: markup-only
*.razor + *.razor.cs partial class (no @code). Routes: [Route(Routes.*)] in code-behind; constants in Routes.cs.
- Feature-oriented / vertical-slice layout:
Features/{FeatureName}/ (page + services + components per feature); shared shell in Layout/.
- Do not modify Application for PWA-only flows — adapters live in
VRT.Resume.Pwa.
- MVC is legacy (planned retirement) — touch only when necessary; new UI work goes to PWA.
- EF providers in hosts only: Persistence →
Relational; Pwa → SqliteWasm; Mvc/Tests → SqlServer.
- EF Core 10.0.8 pinned for SqliteWasmBlazor 0.9.1-pre compatibility.
- WASM startup:
BlazorWebAssemblyLoadAllGlobalizationData=true; MudBlazor.min.js before Blazor script; MudDrawer → Persistent + Breakpoint.Md.
- Details:
AGENTS.md → section VRT.Resume.Pwa.
Common pitfalls
- Build with
VRT.Resume.sln (not bare dotnet build in repo root).
- Respawn 7 needs
SqlConnection, not connection string.
- SkiaSharp 4 uses
SKSamplingOptions for resize.
GetResumeListQuery / GetProfileImageQuery do not use Result<T>.
Verification checklist
dotnet build VRT.Resume.sln -c Release
dotnet test VRT.Resume.sln -c Release
Fix nullable warnings properly (string?, ?? with intentional defaults) — do not suppress without reason.
Extended reference
Full inventory, entity map, controller routes, auth flow, Azure deploy: AGENTS.md
When you learn something new about this codebase that future agents should know, append it to AGENTS.md.
