winforms
WPF
winforms | WPF | |
---|---|---|
25 | 50 | |
4,212 | 6,816 | |
0.6% | 0.5% | |
9.3 | 9.7 | |
6 days ago | 5 days ago | |
C# | C# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
winforms
-
Ask HN: Any way to write a simple desktop app anymore?
Windows Forms[0] is still alive and will never die, and very low overhead to start with, and works on new and shiny .NET 8.
If Linux or macOS, you can use AvaloniaUI[1] instead which is sufficiently advanced but assumes some prior knowledge.
[0] https://github.com/dotnet/winforms/blob/main/docs/getting-st...
[1] https://docs.avaloniaui.net/docs/get-started/
- A GitHub issue suggests the removal of the WebBrowser control in WinForms. If you think this is a bad idea, be sure to voice your disapproval on the issue!
-
Duda carrera: C#/.NET vs. Node/Express
Winforms: Licencia MIT.
-
We Got the Generics We Have (2022)
3. Therefore reified generics are not possible to implement in a backwards compatible way.
Ok, sure, but if you instead a new generic collection types and leave the old ones alone, you don’t have to worry about breaking existing compiled code.
This comment about C# suggests a lack of familiarity with the approach C# took:
> C# made the opposite choice — to update their VM, and invalidate their existing libraries and all the user code that dependend on it.
All of the pre-generic C# libraries continue to exist to this day (ArrayList, HashTable, and the non-generic IEnumerable). Applications that used them never stopped working. New code uses the generic collections (List and Dictionary).
Anyways, I think the costs that Java is currently paying for non-reified generics (reflection, performance, and type safety mentioned in the article) is not worth the backwards comparability with the 20 year old J2SE 1.4. The price C# pays for making a backwards incompatible generics (mostly some minor annoyance when designing a collection class implementing IEnumerable) is worth it at this point.
P.S. ok, I do admit that C# forking the collection library is still causing ongoing maintenance work 18 years later: https://github.com/dotnet/winforms/pull/8673
-
When A .NET Developer Learns Blazor
No, it is fully supported and in active development. https://github.com/dotnet/winforms
-
WPF Roadmap 2023
No, it's still under active development/maintenance. https://github.com/dotnet/winforms/graphs/contributors
-
Where are these images stored?
The image is kept in-memory— https://github.com/dotnet/winforms/blob/main/src/System.Windows.Forms/src/System/Windows/Forms/PictureBox.cs
-
Does anyone know how to make a UITypeEditor for Winforms that works in .NET 6?
Appears that this has been broken for a while. Seems it has something to do with the new designers being run out of process.
-
Why is Microsoft's C# not taught in most universities and Java is instead?
Also, the runtime that C# runs on, is also completely open source as well (https://github.com/dotnet/runtime); ASP.NET which is used to create web apps in C# is open as well (https://github.com/dotnet/aspnetcore). WinForms/WPF, used to make desktop apps in C# is also open source (https://github.com/dotnet/wpf, https://github.com/dotnet/winforms). All of the source code for these are on the dotnet Github page: https://github.com/dotnet and most are all MIT-licensed.
-
Announcing .NET 7 Preview 5
You'll likely have to open an issue against https://github.com/dotnet/winforms. If you've already opened an issue here, then feel free to link and I might be able to provide suggestions on how to improve the triage process.
WPF
-
.NET 8 is on the Way! 7 Features that will blow your mind 🤯
Gear up, folks, and test drive this fresh-off-the-lab feature. And should you stumble upon any glitches along the way, don’t hesitate to reach out. Got a bug to report or feedback to give? Send them directly to our dotnet/wpf repository. We’re eager to hear from you, because together, we’re only going to make the experience even better!
- What is the best for Develop Cross-platform Application ?
-
MAUI Part 2: A New Page And Basic Styling
I did some research and did not find any proof of the EOL on WPF. In fact, Microsoft just updated the roadmap on WPF 2 months ago.
-
Avalonia UI for .NET: Project Overview from Mike James
There’s still room for improvement though. I should add, WPF on .NET Core consumes a lot of memory, due to a memory leak. It was logged by our COO as one of our users was doing a comparison.
-
VS2022 Build Error: 'Could not load file or assembly 'PresentationFramework, Version=6.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
have you tried this?
-
Duda carrera: C#/.NET vs. Node/Express
WPF: Licencia MIT.
- Help make hyphen ligatures a thing by expressing your interest in this GitHub issue
-
Just switched to this from GOG. Playnite is great, I only have one complaint...
Some added context: It's a side effect of how variable rendering works in UI library we use. There's currently sadly no way how to disable VRR compatibility, which causes the issue you describe unless you tell your GPU to not treat Playnite as VRR compatible. Some more info here.
-
Something Pretty Right: The History and Legacy of Visual Basic
WPF is definitely not dead. It may not be the latest shiny thing, but it works, it is maintained (judging by https://github.com/dotnet/wpf or https://devblogs.microsoft.com/dotnet/wpf-on-dotnet-7/), and it is fully and officially supported on the modern .NET platform.
-
WPF Begins Its Long Goodbye
This article only sights a video stream. I think part of the problem with the glacial pace of development is reliance on manual testing. See this comment:
https://github.com/dotnet/wpf/discussions/7130#discussioncom...
> Our primary goal is to ensure reduced turn-around-times for new PRs as well as clear the pending backlog of existing PRs. To that end, we are working on putting appropriate automation in place to reduce the dependency on manual testing as much as we can.
See also the recently updated WPF roadmap:
https://github.com/dotnet/wpf/blob/main/roadmap.md
If you look at the history of this file you can over the years tests have been always been in the backlog.
As for “where projects go to die”, they have 3 features planned for this year: Windows 11 Theming, a new type of folder browser, and null ability annotations. And they say they don’t think they can do them all. Maybe I’m underestimating, but that’s not a lot.
What are some alternatives?
Avalonia - Develop Desktop, Embedded, Mobile and WebAssembly apps with C# and XAML. The most popular .NET UI client technology
Introducing .NET Multi-platform App UI (MAUI) - .NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.
Xamarin.Forms - Xamarin.Forms Official Home
Flutter - Flutter makes it easy and fast to build beautiful apps for mobile and beyond
Visual Studio Code - Visual Studio Code
imgui - Dear ImGui: Bloat-free Graphical User interface for C++ with minimal dependencies
Unity-WinForms - A Windows Forms port for Unity3d
Extended WPF Toolkit™ - All the controls missing in WPF. Over 1 million downloads.
Windows UI Library - Windows UI Library: the latest Windows 10 native controls and Fluent styles for your applications
Uno Platform - Build Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported.