القائمة
Build a believable mid-2000s .NET data layer around connection catalogs, stored-procedure wrappers, DataSets, and repository facades.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Squad branching model: main-only workflow with feature branches
{what this skill teaches agents}
Wire legacy .NET Framework service hosts through Enterprise Library-flavored appSettings so Unity, service location, exception policies, logging, and database aliases all hang off one configuration seam.
Build internal order-management Web Forms pages with ObjectDataSource, GridView, DetailsView, and ViewState-heavy filter handling.
Anchor store-ops workbench screens in separate StoreOps tables for order state, status snapshots, workforce alerts, and zone bulletins, with dispatch tickets linked back to orders.
Restack a child PR onto main after its base PR merges, then revalidate before clearing draft.
| name | legacy-dal-seam |
| description | Build a believable mid-2000s .NET data layer around connection catalogs, stored-procedure wrappers, DataSets, and repository facades. |
| domain | services |
| confidence | high |
| source | earned |
Use this when a legacy .NET sample needs a data access layer that feels real enough for modernization tooling, but you do not want to hide the rough edges behind a modern ORM abstraction.
StoreOps, CustomerHub, Reporting).DataSet/DataTable shapes.DataSet plumbing, even if the repository internals stay ugly.Configuration\LegacyConnectionCatalog.csStoredProcedures\LegacyStoredProcedures.csGateways\LegacyDbGateway.csRepositories\StoreOps\...Repository.csRepositories\CustomerHub\...Repository.csRepositories\Reporting\...Repository.csIntegrations\...\Job.cs consuming a repository-backed batch snapshot