-
Notifications
You must be signed in to change notification settings - Fork 178
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
WinForms for .NET 5+ Planning #72
Labels
doc-idea
Indicates issues that are suggestions for new topics [org][type][category]
dotnet-desktop/svc
Pri3
Low priority
winforms/subsvc
Comments
Thraka
changed the title
WinForms for .NET Core 3.0 Planning
WinForms for .NET 5+ Planning
Apr 23, 2020
This was referenced Oct 13, 2020
This was referenced Oct 13, 2020
adegeo
added
📚 Area - .NET
doc-idea
Indicates issues that are suggestions for new topics [org][type][category]
and removed
⌚ Not Triaged
Not triaged
labels
Oct 13, 2020
This was referenced Oct 26, 2020
Merged
adegeo
added
dotnet-desktop/svc
winforms/subsvc
and removed
🗃️ Technology - WinForms
labels
Feb 4, 2021
This was referenced May 18, 2021
This was referenced May 18, 2021
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
Pri3
Low priority
winforms/subsvc
Planning content for Desktop Guide - WinForms portion.
Update We should redesign this plan like the WPF plan was designed: evaluate each article in the .NET Framework for value, and redesign the TOC below to include each new article specifically.
The current overall plan is to:
Content plan items
This requires an update with info from order of events
This content should mirror what is in WPF. This content doesn't really exist in the .NET Framework winforms area
Custom designers for .NET require new namespace and type Custom Designers for .NET 5 require different design namespace and type #41
.NET Framework 4 TOC and my notes
The text was updated successfully, but these errors were encountered: