Menü
Seed a legacy .NET Framework core library with Unity registrations, a CommonServiceLocator bridge, and small cross-domain business policies before the host projects wire the container.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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-unity-core-seam |
| description | Seed a legacy .NET Framework core library with Unity registrations, a CommonServiceLocator bridge, and small cross-domain business policies before the host projects wire the container. |
| domain | architecture |
| confidence | high |
| source | earned |
Use this when a legacy sample needs an authentic Enterprise Library-era DI seam, but the web/service/desktop hosts are not ready to own full composition roots yet.
CreateConfiguredContainer() owns registration for fresh containers, while InitializeServiceLocator(...) only attaches the locator to an already-configured container.new calls everywhere.