Description
Related to #72
When porting and migrating source content (presented as a link that goes to an article), open the source material up. Find out where it exists in the TOC. In the source project #72 navigate down to the .NET Framework 4 TOC and my notes collapsible region and expand it. Find the article title in the TOC and review the notes.
Tasks
- Header crafted for .NET Framework control designer content. Explain that this content was written for .NET Framework and may not apply to .NET. Link to this content's overview.
- Apply header to archived VS 2011 content (linked to by the API docs)
Supplemental
Relevant blog posts:
-
WinForms Designer for .NET general overview and motivation of the rewrite
State of the Windows Forms Designer for .NET Applications -
Databinding with the OOP-Designer
-
Note, that the Data Source Provider Service are not available in .NET (Core) scenarios. That means, that we also don’t have the Data Sources Window, which allows to drag elements on the Form, which then get automatically prepared for binding.
Databinding with the OOP Windows Forms Designer - .NET Blog -
This one is for MVVM in WinForms. It would be cool to teach SEO MVVM and WinForms, so if people look for it, they wouldn’t find 10 year old Stack-overflow-workarounds.
Using Command Binding in Windows Forms apps to go Cross-Platform - .NET Blog
-
-
User Controls in the new Designer:
-
The blog post does only do a semi-good job I think for the really easy scenarios. Contact @KlausLoeffelmann if we need to come-up with something easy for introduction.
Custom Controls for WinForm's Out-Of-Process Designer - .NET Blog -
For VB, maybe add some info boxes to the existing articles for the Application Framework articles, and link them to this Blog Post, which summarizes the changes. The links to those docs are in the blog post (so those would just need a back-link to the post):
What's new for the WinForms Visual Basic Application Framework - .NET Blog
-
-
Review email for more information...
-
How to add custom smart tag on .net6 WinForms in design mode? winforms#8873
Proposed TOC
- Develop controls
Custom designers for .NET require new namespace and type Custom Designers for .NET 5 require different design namespace and type #41- Overview (link link link)
- Design guidelines (link link)
- Extend controls (link)
- Composite user controls
- User-drawn controls Develop controls - User drawn controls #1667
The cut articles from this section are mostly cut because we'll be porting them in a different way to support how designers are done in .NET. TheOnPaint
article is cut because the information is in the Overview. - Visual Studio designer support
This is changing completely for .NET 6/7. This content needs to be reviewed before its ported and it shouldn't be done by myself, but probably by a winforms team member.