-
Notifications
You must be signed in to change notification settings - Fork 968
Issues: dotnet/winforms
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[A11Y] Expose ClientSize property for forms
area-VSDesigner
Windows Forms out-of-proc designer related issues
untriaged
The team needs to look at this issue in the next triage
#12183
opened Sep 19, 2024 by
towebo
[A11Y] Property Editor drop down value pickers are sometimes hard to use with keyboard and screen reader
area-VSDesigner
Windows Forms out-of-proc designer related issues
untriaged
The team needs to look at this issue in the next triage
#12182
opened Sep 19, 2024 by
towebo
[A11Y] Screen Reader doesn't announce what control gets focused
area-VSDesigner
Windows Forms out-of-proc designer related issues
untriaged
The team needs to look at this issue in the next triage
VS Designer still does not add name property in designer.cs file for ListView ColumnHeader Types
area-VSDesigner
Windows Forms out-of-proc designer related issues
[LOC]The "on" is not translated for Error on errorProvider property on all local languages
area-VSDesigner
Windows Forms out-of-proc designer related issues
tenet-localization
Suggested translations of resources; notification requiring translations; internationalization
When Designer emits files comments have a period and 2 space and a space after period at end of some lines.
area-VSDesigner
Windows Forms out-of-proc designer related issues
Priority:3
Work that is nice to have
#12026
opened Aug 31, 2024 by
paul1956
Cursor property cannot be set to "Arrow" in designer
area-VSDesigner
Windows Forms out-of-proc designer related issues
tracking
Opening ProgressDialog is this repo causes Designer to crash with Timed out while connecting to named pipe.
area-VSDesigner
Windows Forms out-of-proc designer related issues
untriaged
The team needs to look at this issue in the next triage
#11749
opened Jul 25, 2024 by
paul1956
Data Bindings should use (1) Early API idea and discussion, it is NOT ready for implementation
area-Binding
Impacting DataBinding
area-VSDesigner
Windows Forms out-of-proc designer related issues
tracking
nameof
instead of raw string literals.
api-suggestion
In .NetCore project, Changes made in the Designer not being Serialized in the Designer.cs file.
area-VSDesigner
Windows Forms out-of-proc designer related issues
untriaged
The team needs to look at this issue in the next triage
#11664
opened Jul 12, 2024 by
Sekar47
Microsoft.DotNet.DesignTools.Client.DesignToolsServerException: Could not resolve type, 'System.ComponentModel.ComponentEditor
area-VSDesigner
Windows Forms out-of-proc designer related issues
untriaged
The team needs to look at this issue in the next triage
#11650
opened Jul 10, 2024 by
PLDAWOL
Can't Bind a Custom IBindingList Component to Controls at DesignTime in .NET 8
area-Binding
Impacting DataBinding
area-VSDesigner
Windows Forms out-of-proc designer related issues
Unable to switch the tabs using mouse. Only switching the tab can be done through TabKey navigation at DesignTime
area-VSDesigner
Windows Forms out-of-proc designer related issues
untriaged
The team needs to look at this issue in the next triage
#11642
opened Jul 9, 2024 by
Sekar47
Assembly.GetType Throws Exception When Using ControlDesigner in Netcore using Microsoft SDK
area-VSDesigner
Windows Forms out-of-proc designer related issues
untriaged
The team needs to look at this issue in the next triage
#11566
opened Jun 20, 2024 by
ChidanandMurugaiah
Button's DialogResult.Ok is not removed from the .Designer.cs even when this button stops from being the form's AcceptButton.
area-VSDesigner
Windows Forms out-of-proc designer related issues
📚 documentation
Documentation bug or improvement
#11537
opened Jun 15, 2024 by
nangelgr
Winform Designer generates confliting resource files on partial class
area-VSDesigner
Windows Forms out-of-proc designer related issues
🪲 bug
Product bug (most likely)
tenet-compatibility
Incompatibility with previous versions or with WinForms for .NET Framework
tracking
#11411
opened May 22, 2024 by
CyrilPaulus
Allow internal types to be selected as object data source for binding
area-Binding
Impacting DataBinding
area-VSDesigner
Windows Forms out-of-proc designer related issues
Using WinForms Controls provided via NuGet inside the Out-Of-Process Designer without copying them to the build output
area-DesignerSupport
area-VSDesigner
Windows Forms out-of-proc designer related issues
tenet-compatibility
Incompatibility with previous versions or with WinForms for .NET Framework
System.Data.DataColumn serializes some properties with a default value (different from the .NET Framework)
area-VSDesigner
Windows Forms out-of-proc designer related issues
💥 regression-release
Regression from a public release
tracking-external-issue
An issue is caused by an external system and won't be fixed in this repo
Add ability to customise Winforms Designer Shadow Cache behaviour
area-VSDesigner
Windows Forms out-of-proc designer related issues
Assembly resolving logic in Out-Of-Process WinForms Designer does not work for *.Resources.dll Assemblies
area-VSDesigner
Windows Forms out-of-proc designer related issues
Re-occurrence of WinForms designer failing to load (was #8996)
area-VSDesigner
Windows Forms out-of-proc designer related issues
UserControls with type parameters cannot be designed in .NET Core
area-VSDesigner
Windows Forms out-of-proc designer related issues
tenet-compatibility
Incompatibility with previous versions or with WinForms for .NET Framework
tracking
Designer not loading: System.InvalidOperationException: Designer load encountered an error. Please ensure that the project can be built successfully.
area-VSDesigner
Windows Forms out-of-proc designer related issues
.NET Core designer uses LicenseManager.UsageMode = LicenseUsageMode.Runtime instead of LicenseUsageMode.Designtime
area-VSDesigner
Windows Forms out-of-proc designer related issues
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.