Obs Arrastre Wpf

Implementation Guidance

• Prefer straightforward WPF structure first: Views, ViewModels, Models, Services, Infrastructure.
• Keep code-behind light. Put domain and stateful behavior in view models or services unless the change is purely visual.
• For data access in the desktop app, prefer injecting IDbContextFactory<AppDbContext> instead of keeping a long-lived DbContext.
• Preserve schema naming intentionally. If introducing C# model names that differ from SQL names, document the mapping in code.
• Avoid speculative libraries and infrastructure before there is a concrete need.
• Keep files UTF-8 encoded, especially XAML and markdown, to avoid broken accents.
• Write repository documentation in Spanish.
• Write Git workflow messages in Spanish, including commit and merge messages.

Domain-Driven Work

• Use references/domain-context.md as the first summary of the SQL schema.
• If the reference and docs/esquema.sql disagree, trust docs/esquema.sql.
• For persistence-related tasks, identify the affected tables, foreign keys, and unique indexes before changing code.

Validation

• For project changes, run dotnet build .\OBSArrastre2026.sln.
• For future tests, prefer solution-level execution from the repo root.

Resources

references/

• references/domain-context.md: concise domain summary derived from docs/esquema.sql.