Skip to content

DesignerAttributes referencing nonexisting classes #2411

@weltkante

Description

@weltkante
  • .NET Core Version: 5.0 master
  • Have you experienced this same bug with .NET Framework?: No

Problem description:
Regression in many (but not all) DesignerAttribute annotations, all attributes have been ported from .NET Framework but a lot of Designer classes they are referencing have not been ported. Discovered during implementation of PR #2230 which is testing the consistency of attribute annotations.

Actual behavior:
[DesignerAttribute] referencing a type which does not exist

Expected behavior:
One of these options needs to be chosen for each designer:

  • remove the DesignerAttribute and provide no designer
  • remove the DesignerAttribute in WinForms, but port the Designer within VS and add the attribute dynamically in the VS Designer environment
  • port the Designer class into WinForms

Which choice to make should be primarily driven by whether you want to support that control being used in a 3rd party designer (requires option 3)

Minimal repro:
PR #2230 test failures when removing skipped entries

List of classes failing the test:

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions