Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Feature Request]: Use the WinForms Designer Extensibility SDK for .NET
See original GitHub issueSince MS is having issues supporting the WinForms designer in .NET, the WinForms Designer Extensibility SDK could be the solution for the current designer issues
Issue Analytics
- State:
- Created 2 years ago
- Comments:18 (18 by maintainers)
Top Results From Across the Web
State of the Windows Forms Designer for .NET Applications
The Windows Forms designer for .NET applications is here, the blog post will give you insights into the new architecture and changes been ......
Read more >microsoft/winforms-designer-extensibility
How to create Control Designers/Type Editors for the out-of-process .NET Windows Forms designer using Visual Studio solution templates.
Read more >winforms/docs/designer/readme.md at main
NET UI framework for building Windows desktop applications. ... Details about how to use the WinForms Designer Extensibility SDK and structure a control ......
Read more >How to write WinForms Designers in NET 6.0
I need to create WinForms project with components under the .net library version 6.0. But when I create the project and the ControlLibrary...
Read more >In VS 2022, WinForms Designer Still Chasing Parity with . ...
NET Framework designer, providers for 3rd party controls for .NET will need to use a dedicated WinForms Designer SDK to develop custom Control ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have had an inspiration from the “Read between the lines of why the above is solving things”
If I
Remove “ALL” designers references from the toolkit e.g.
Set toolkit project to be “Only” net5 windows
Create a new winform net 5 windows only main app
build.
I get the following showing up in the toolbox:
I’ll need to investigate further to see “What” the designers are attempting to do; but so far I’ve been able to drag (A random selection not all) controls onto the form !
It’s not ideal, but maybe private nightly packages could be used for testing?