-
Notifications
You must be signed in to change notification settings - Fork 177
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
[epic] WinForms Developing User Controls - Move and port content #1070
Labels
doc-idea
Indicates issues that are suggestions for new topics [org][type][category]
dotnet-desktop/svc
Pri1
High priority, do before Pri2 and Pri3
winforms/subsvc
Comments
adegeo
added
the
doc-idea
Indicates issues that are suggestions for new topics [org][type][category]
label
May 18, 2021
adegeo
added
Pri1
High priority, do before Pri2 and Pri3
and removed
Pri3
Low priority
labels
Apr 11, 2023
Looks very good, thanks! |
This is incredible, thank you! |
github-actions
bot
added
📌 seQUESTered
Label to indicate an item has been imported.
and removed
🗺️ reQUEST
Trigger label to import an issue into Quest
labels
Apr 12, 2023
This was referenced Jun 17, 2023
This was referenced Jul 5, 2023
adegeo
changed the title
[winforms-dotnet5] Move content - Develop controls
[epic] WinForms Developing User Controls - Move and port content
Jul 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
doc-idea
Indicates issues that are suggestions for new topics [org][type][category]
dotnet-desktop/svc
Pri1
High priority, do before Pri2 and Pri3
winforms/subsvc
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
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
Custom designers for .NET require new namespace and type Custom Designers for .NET 5 require different design namespace and type #41
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.
Associated WorkItem - 84626
The text was updated successfully, but these errors were encountered: