Provide an AI assistant for code generation with the Telerik UI for WinForms controls. 

Such as Telerik Blazor AI Coding Assistant

Steps to Reproduce:

1. Create a new WinForms application targeting .NET 9.

2. Add a RadStatusStrip to the main form.

3. Run the application.

4. Snap the form to the left or right edge of the screen (using Windows Snap).

5. Minimize the form.

6. Restore the form.

Expected Behavior:
The form should maintain its original size and remain fully visible on screen after being restored.

Actual Behavior:
Every time the form is minimized and restored, it increases in height. After a few cycles, the bottom part of the form — including the RadStatusStrip — becomes hidden behind the Windows taskbar (Start menu).

Additional Info:

• The issue only occurs when a RadStatusStrip is added to the form.

• The issue does not occur when using a standard StatusStrip from WinForms.

• The problem occurs consistently and can be reproduced easily.

• Tested both in debug mode and with a compiled executable.

Attachments:

• Screenshots (before and after restore).

• Sample reproduction project (if needed).

  This is only repeated in windows 10

   

Using specifically Win11 Compact DARK theme has additional space compared to the Win11 Compact LIGHT theme. See the pictures.

• On Light theme there are 4 pixels between the form border and the top border of a tab.
• On Dark theme there are 12 pixels between the form border and the top border of a tab.

In my opinion the dark theme has a wrong height here and the light theme is correct, especially compared to other themes, even Office 2019 for example.

Light theme:

Dark theme:

When I use the new project wizard provided by Microsoft for a new windows forms project it lets me select the target .net version

When I do the same with the Telerik wizard, it does not let me choose what .net Version I'm targeting and does not generate the optimal code for the target version. For example when I target .net 9.0 with high dpi support, it should generate API calls for High DPI, not an entry in the app manifest. IMHO the generated code should be as close to the Microsoft Standard for the targeted .net version as possible. 

I would like to see a new property added to the RadLabel control: Style. Style is an enumeration with layout styles like in MS-Word: 

• Normal
• Title
• Heading 1
• Heading 2
• etc.

When the style is applied, the styling (font, color, background, etc.) is applied conform the currently active Theme. Therefor all themes need to be expended to support this setting.

Of course the enum label 'Custom' should be present (or null) when a user tries to override the style-related properties (like font, color, background, etc.)

This is very usefull when a programmer wants to build his own form (with or without Layout / Flow controls).

Telerik already uses it a bit themselves: Some (data entry) controls already generate (group) headers and captions in there forms. 

Any anchor setting works, except for right + left, then the controls start to behave weird. 

this.radMultiColumnComboBox4.Anchor = AnchorStyles.Left | AnchorStyles.Right;
this.radTextBoxControl2.Anchor = AnchorStyles.Left | AnchorStyles.Right;
this.radSpinEditor4.Anchor = AnchorStyles.Left | AnchorStyles.Right;
this.radDropDownList4.Anchor = AnchorStyles.Left | AnchorStyles.Right;

this.radMultiColumnComboBox3.Anchor = AnchorStyles.Left | AnchorStyles.Right;
this.radDropDownList3.Anchor = AnchorStyles.Left | AnchorStyles.Right;
this.radSpinEditor3.Anchor = AnchorStyles.Left | AnchorStyles.Right;
this.radTextBoxControl1.Anchor = AnchorStyles.Left | AnchorStyles.Right;

Hi All.

Could you please add or let me know locators for "RadChat" window for Automation purpose. I am unable to find locators on the below area.

In.NET8 Microsoft has released databinding improvements: What's new in Windows Forms .NET 8 - Windows Forms .NET | Microsoft Learn. Add Command Binding and DataContext Support in .NET 8+

Documentation about High-DPI mechanisms available on the website is very outdated and mostly does not consider the changes and improvements that Microsoft made with .net 7.0 and 8.0.

What's needed is thorough documentation about Telerik's behavior in comparison with the different situations on .net Framework 4.9 and the major .net Versions 6.0, 7.0, and 8.0.

Kind regards

Erwin