fabrikam-controls-rules
Fabrikam UI control rules that apply during a .NET version upgrade — which Fabrikam.Windows.Forms versions are supported on modern .NET, what must be replaced rather than retargeted, and how the decision is recorded.
- License 许可
- MIT
- 最近更新
- 2026-10-24
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- fabrikam-controls-rules
- metadata
- { "order": 100, "scope": [ "Assessment", "Planning", "IntegrityReview" ], "traits": ".NET|CSharp|VisualBasic", "discovery": "scenarioExtension", "extends-scenario": [ "dotnet-version-upgrade" ], "scopeInstructions": { "Planning": "scopes/planning.md", "Assessment": "scopes/assessment.md" } }
- description
- Fabrikam UI control rules that apply during a .NET version upgrade — which Fabrikam.Windows.Forms versions are supported on modern .NET, what must be replaced rather than retargeted, and how the decision is recorded.
02 资源文件 2
- 参考文档scopes/assessment.md1.5 KB
- 参考文档scopes/planning.md2.4 KB
03 SKILL.md 正文
Fabrikam UI controls during a .NET version upgrade
Fabrikam ships the Fabrikam.Windows.Forms control suite. We own its support
policy, and the platform's own compatibility data does not describe it — so a
.NET version upgrade must not decide anything about these packages without our
input.
The one rule that always holds: Fabrikam.Windows.Forms before 8.0 is not
supported on .NET 8 or later. Those references must be replaced with 8.x,
not retargeted. Do not infer a policy for a Fabrikam.* package that is not
named in our guidance — ask instead.
This body is what the IntegrityReview scope is served, because that scope is
declared in scope but deliberately left out of scopeInstructions. When
reviewing the resulting change, confirm that:
- no project targeting .NET 8+ still references
Fabrikam.Windows.Forms< 8.0; - every designer file touched by the bump was regenerated, not hand-edited;
- no
Fabrikam.Windows.Forms.Themesreference survives.
This skill is a scenario extension: it defines no workflow of its own and is
never user-selectable. It adds Fabrikam's rules to the scenario named in
extends-scenario, at the three points named in scope.
Two things to change when you copy this sample:
extends-scenario: [dotnet-version-upgrade]is a placeholder. Confirm the real scenario id in your environment — an id that matches nothing fails silently. If your guidance is cross-cutting, omit the field instead of guessing.order: 100only fixes presentation sequence when several extensions match (ascending; omitted sorts last). It does not arbitrate conflicts. 100 is just a round mid-range value.
traits (.NET|CSharp|VisualBasic) gates on the repository — a separate filter
from extends-scenario and scope. All three must pass for this content to be
served.
04 同仓库更多 Skills
fabrikam-v4-upgrade
Migrate a .NET solution from the Fabrikam v3 component suite to v4 — apply the package renames (Fabrikam.Web.Mvc → Fabrikam.AspNetCore.Mvc, Fabrikam.Logging → Fabrikam.Diagnostics, Fabrikam.Security.Tokens → Fabrikam.Identity.Tokens), bump Fabrikam.Data to 4.0, and drop Fabrikam.Json in favor of System.Text.Json.
fabrikam-package-audit
Audit a .NET project's Fabrikam package references for v4 readiness — find v3-era Fabrikam.* packages, flag the ones that are renamed, version-bumped, or removed in v4, and report a per-package upgrade plan. Use when reviewing .csproj, Directory.Packages.props, or packages.config.
fabrikam-v4-upgrade
Migrate a .NET solution from the Fabrikam v3 component suite to v4 — apply the package renames (Fabrikam.Web.Mvc → Fabrikam.AspNetCore.Mvc, Fabrikam.Logging → Fabrikam.Diagnostics, Fabrikam.Security.Tokens → Fabrikam.Identity.Tokens), bump Fabrikam.Data to 4.0, and drop Fabrikam.Json in favor of System.Text.Json.
fabrikam-package-audit
Audit a .NET project's Fabrikam package references for v4 readiness — find v3-era Fabrikam.* packages, flag the ones that are renamed, version-bumped, or removed in v4, and report a per-package upgrade plan. Use when reviewing .csproj, Directory.Packages.props, or packages.config.
fabrikam-controls-rules
Fabrikam UI control rules that apply during a .NET version upgrade — which Fabrikam.Windows.Forms versions are supported on modern .NET, what must be replaced rather than retargeted, and how the decision is recorded.