-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Closed
Labels
area-DesignerSupporttenet-compatibilityIncompatibility with previous versions or with WinForms for .NET FrameworkIncompatibility with previous versions or with WinForms for .NET Framework
Description
- .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:
- Is the InitializeExistingComponent method implementation going to change in .NET Core?
- Is the Site.Name property going to be assigned as the DefaultProperty value in the .NET Core implementation of the InitializeNewComponent method?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area-DesignerSupporttenet-compatibilityIncompatibility with previous versions or with WinForms for .NET FrameworkIncompatibility with previous versions or with WinForms for .NET Framework