Skip to content

Research Designer-safe service assignment and UI scope ownership #14948

Description

@KlausLoeffelmann

Objective

Validate whether a marker/assignment contract, generated hookup code, activation factory, or another pattern best bridges parameterless Designer creation and runtime DI. Include Forms, UserControls, components, inherited forms, nested controls, modal dialogs, and out-of-process Designer constraints. Define scope ownership and disposal rules.

Completion guidance

  • Keep the implementation focused on the objective while allowing the assignee to improve the approach based on research.
  • Document important decisions, rejected alternatives, dependencies, and follow-up work.
  • Add or update tests and documentation appropriate to the work.
  • Verify locally and in CI where the task changes code or generated artifacts.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Review IssueIssue content and decomposition require team review and may be iterated

    Type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions