Cursor property cannot be set to "Arrow" in designer

[accellbtjsteens]

Environment

Visual Studio version 17.10.6

.NET version

8.0

Did this work in a previous version of Visual Studio and/or previous .NET release?

Yes, unknown

Issue description

When the Cursor is set to "Arrow", it revers back to "Default" in the designer.
This is incorrect, as for some components (such as a textbox), the default cursor isn't an arrow.

Steps to reproduce

1. Drop a textbox unto a blank form.
2. Set the Cursor in Properties to Arrow

Diagnostics

No response

[merriemcgaw]

@accellbtjsteens can you please help us understand the scenario here? Does this occur when you're targeting .NET 9? Has this regressed from a previous version of either .NET or of Visual Studio? Is this something that you see exclusively in the design time experience or can you reproduce this in a runtime scenario?

[Zheng-Li01]

@merriemcgaw @accellbtjsteens, for .NET from 6.0 ~ 9.0 that the default cursor value is default for now, which actually have the same icon as arrow as below screenshot. and get the below returned results.

Core:
The default value is Default
Default -> IBeam=> returned IBeam
Default -> Arrow => returned Default
IBeam-> Default => returned Default
IBeam-> Arrow=> returned Default

Framework:
The default value is "IBeam"
IBeam-> Default => returned Default
IBeam-> Arrow=> returned Arrow
Default -> IBeam=> returned IBeam
Default -> Arrow => returned Arrow
Arrow -> Default => returned Default

[accellbtjsteens]

@merriemcgaw This is a design time issue related to the designer.
When selecting "Arrow" from the drop down list in the Properties pane, the selection is not taken over. Instead, it reverts to "Default" (and the default for a TextBox is not Arrow). If you run it, there will be an Ibeam when hovering over the textbox instead of an arrow.
When setting the cursor to Arrow in the code behind, everything works as intended.

In the post above by Zheng-Li01 you can see this behavior in the first video.

I have verified that the same issue occurs with VS 2022 17.11.2. .NET 5 till 8 all show the same behavior.
When using a .NET Framework project, the issue does not occur.

[merriemcgaw]

@Zheng-Li01 can you copy this issue over to the internal designer repo? We'll update this once we have a fix.

[Zheng-Li01]

@merriemcgaw copied the issue as https://github.com/microsoft/winforms-designer/issues/6079 in the internal designer repo.