In .NET 8 WinForms, using the PropertyGrid at runtime, the DataSource property of the ComboBox appears disabled.

[ravipoddar10mca]

In .NET 8 WinForms, the DataSource property of the ComboBox appears disabled in the PropertyGrid control.

[elachlan]

@Olina-Zhang can your team please test and confirm?

[Zheng-Li01]

The issue can reproduce from .NET Core 3.1 to 8.0 for the controls which support the DataSource property, such as ComBobox, DataGridView, ListBox, BingingSource etc. cannot reproduce NET 9.0 & latest 10.0 as below screenshot. but for .NET 9.0 & 10.0, the "Add new Object Data Source..." function cannot be used.

[elachlan]

@Zheng-Li01 Is there a designer issue for this?

[Zheng-Li01]

@Zheng-Li01 Is there a designer issue for this?

Sorry about this, have correct my test results. please have a check.

[ravipoddar10mca]

Please solve this issue in .NET8

[ravipoddar10mca]

@elachlan @Zheng-Li01

Is there any workaround for that ?? and when we expect the resolution in .NET8

[KlausLoeffelmann]

I am not entirely sure what folks would expect here.
The functionality which we provide in the Visual Studio Out-Of-Proc Designer is bound to Visual Studio, and not part of the runtime.

Please note that every functionality which is ultimately shown in the Property Grid is controlled by the respective TypeEditors.

When we needed a different approach in .NET 6+, we rerouted the path to get the DataSource's TypeEditor. That is always an option to do that, if not - for different domain-specific scenarios - a necessity.

So, I did not watch the changes around this. But going forward, we could have a StringEditor for any DataSource property at best.

If you want to have something specific, it's comparatively easy to do that.

Here are a couple of resources to read on from. This is all very well documented!

https://learn.microsoft.com/dotnet/api/system.drawing.design.uitypeeditor?view=windowsdesktop-9.0

What's important is:
This scenario is documented for design-time but will for .NET Core only work at runtime.
That is expected and also documented:

https://learn.microsoft.com/dotnet/desktop/winforms/controls-design/designer-differences-framework?view=netdesktop-9.0

If you need more background, why this works that way, take a look at this blog post I wrote quite a while ago:

https://devblogs.microsoft.com/dotnet/custom-controls-for-winforms-out-of-process-designer/

If you have additional questions, or if I have missed anything around this, please follow up.

Thanks!

[KlausLoeffelmann]

Closing this as won't fix because it's not a bug.
If you feel this is a bug, feel free to reopen this, and we can discuss this further.