Migrate DB schema to SQL project, refactor forms & UI #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Migrate DB schema to SQL project, refactor forms & UI
Sql.sqlproj); remove EF Core migrations and entity builders.sqlfiles with simple names[Table]attributes to match new table namesPR Classification
Design and infrastructure refactor to migrate database schema management from EF Core migrations to a Visual Studio SQL Project, with related UI and resource improvements.
PR Summary
This PR removes all Entity Framework migrations and entity builders, introducing a SQL Project as the sole source of truth for the database schema, and updates forms and resources for improved usability and bilingual support.
EnrollmentManager.cs,VillageManager.cs).Sql/Sql.sqlprojand all table definitions as.sqlfiles, updating the solution and documentation accordingly.EnrollmentandVillagemodels to use simple[Table("ModelName")]attributes..resx) for both English and Xitsonga to improve validation and section headers.