القائمة
Pattern for a believable back-office ASP.NET Web Forms portal shell
التثبيت باستخدام 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.
Build a believable mid-2000s .NET data layer around connection catalogs, stored-procedure wrappers, DataSets, and repository facades.
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.
| name | legacy-webforms-portal-shell |
| description | Pattern for a believable back-office ASP.NET Web Forms portal shell |
| domain | web-forms |
| confidence | medium |
| source | earned |
Use this when the sample needs an internal portal that feels like it grew up beside WinForms tools and MVC sites instead of replacing them. It works well for supervisor dashboards, bulletin centers, and admin shells that should look obviously older than the public storefront.
System.Web.Extensions explicitly.ViewBag or older Web Forms AJAX packages, expect to restore packages and add missing framework references before validating the full solution.