winforms
Avalonia
Our great sponsors
winforms | Avalonia | |
---|---|---|
25 | 254 | |
4,212 | 23,749 | |
1.8% | 2.8% | |
9.3 | 9.9 | |
3 days ago | 3 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.
Avalonia
-
Industrial Controller? Windows or Linux?
You might also want to look at AvaloniaUI[0] for a cross platform .NET GUI library. It is similar to WPF but much nicer to work with.
[0] https://github.com/AvaloniaUI/Avalonia
- Avalonia – Farewell to the .NET Foundation
-
AvaloniaUI: Create Multi-Platform Apps with .NET
Production user here. There's no money gotchas. They're above reproach. In fact, I've received considerable free support from their devs on GitHub Issues [1].
The Avalonia business model is based on selling XPF, which runs WPF (Windows-only) apps on other platforms. That's very interesting to big corps with existing codebases.
See my comment [2]
[1] https://github.com/AvaloniaUI/Avalonia/issues
[2] https://news.ycombinator.com/item?id=39246988#39249128
-
.NET on Linux: What a Contrast
Yes, but the portable GUI frameworks by Microsoft themselves are generally not very good, and they tend to be abandoned after a couple of years.
Avalonia is developed outside of the Microsoft corporate madness and seems to be slowly becoming the defacto cross-platform framework because it is expected to last a bit longer than a manager's attention span: https://avaloniaui.net/
- Too many Mac apps are being built with Electron
-
Ask HN: Do you have a problem you'd pay to have taken away?
Not my comment, but relevant here "The problem with compiling Skia to WASM is you'll lose any benefits of hardware graphics acceleration on the device."
(From https://github.com/AvaloniaUI/Avalonia/discussions/6831#disc... )
- Dezvoltare aplicatie desktop
- Ask HN: How to create web, mobile, and desktop apps from a single code base?
-
.NET 8 – .NET Blog
It's a bit of a hit and miss as of today. CLI, back-end and natively compiled libraries (think dll/so/dylib or even .lib/.a - you can statically link NAOT binaries into other "unmanaged" code) work best, GUI - requires more work.
Avalonia[0] and MAUI[1] have known working templates with it, but YMMV.
[0] https://github.com/lixinyang123/AvaloniaAOT / https://github.com/AvaloniaUI/Avalonia/ / honorable mention https://github.com/VincentH-Net/CSharpForMarkup
[1] https://github.com/dotnet/maui (try out with just true in csproj - it is known to work e.g. on iOS)
-
One Game, by One Man, on Six Platforms: The Good, the Bad and the Ugly
For desktop, Avalonia, hands down.
https://avaloniaui.net/
Open source, powered by Skia, backed by JetBrains, and quite battle-tested at this point for small to medium-sized apps. In theory perfectly capable for enterprise as well, since it's basically a spiritual successor to WPF, which has been an industry standard for about 15 years.
They're diving into mobile and WASM well, but that's more of a recent effort and I haven't tested that yet.
What are some alternatives?
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.
Uno Platform - Build Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported.
Xamarin.Forms - Xamarin.Forms Official Home
Visual Studio Code - Visual Studio Code
WPF - WPF is a .NET Core UI framework for building Windows desktop applications.
Unity-WinForms - A Windows Forms port for Unity3d
Eto.Forms - Cross platform GUI framework for desktop and mobile applications in .NET
Windows UI Library - Windows UI Library: the latest Windows 10 native controls and Fluent styles for your applications
MahApps.Metro - A framework that allows developers to cobble together a better UI for their own WPF applications with minimal effort.
Gtk# - Gtk# is a Mono/.NET binding to the cross platform Gtk+ GUI toolkit and the foundation of most GUI apps built with Mono