Skip to content

ComponentDesigner - InitializeNewComponent/InitializeExistingComponent issues #1395

@MrB0nd

Description

@MrB0nd
  • .NET Core Version: 3.0.100-preview8-013006
  • Have you experienced this same bug with .NET Framework?: No

I have a question about the InitializeNewComponent and InitializeExistingComponent methods of the ComponentDesigner class.
 
In .NET Framework, the InitializeNewComponent method implementation contains some code related to DesignerActionUIService. Also InitializeNewComponent calls the OnSetComponentDefaults method that sets the value of the DefaultProperty for the component. InitializeExistingComponent calls the InitializeNonDefault method that does nothing.
 
In .NET Core InitializeNewComponent calls the InitializeNonDefault method. InitializeExistingComponent throws NotImplementedException.
 
So, my questions are:

  1. Is the InitializeExistingComponent method implementation going to change in .NET Core?
  2. Is the Site.Name property going to be assigned as the DefaultProperty value in the .NET Core implementation of the InitializeNewComponent method?

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