winforms
Windows UI Library
winforms | Windows UI Library | |
---|---|---|
25 | 102 | |
4,212 | 6,030 | |
0.6% | 0.8% | |
9.3 | 7.7 | |
5 days ago | 20 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.
Windows UI Library
- WinUI 3 is now open source
- WinUI3 Source Available
- Can't publish WinUI 3 app
- Leaked Microsoft poll shows fewer employees have confidence in leadership
- Should I start migrating my Xamarin app to MAUI
-
When are we going to have smooth animations ?
I wish that was true, but even the new stuff, like their new frameworks, performs poorly while their older frameworks perform really well. That's brand new code, with no legacy codebase to care for.
-
WinUI Unpackaged --- What am I missing?
The reason why I don't recommend Winui is the million bugs it has. See the github issues page. All Microsoft ui stuff sucks currently. But if you use WPF why not FluentWPF
- Visual Studio UI will get redesigned
-
For the past year and a half I've been working on Wintoys, an app that let's you experience Windows in your way and keep it fresh everyday while having everything you need in one place
Development for WinAppSdk and WinUI 3 is also very slow and Microsoft seems to not want to push it and invest more developers into it for some reason. They try to improve the framework, is just it's a small team. For example it was a headacke to apply the Mica backgrop and required unmanaged code, they made it simpler and reduced it to a line of code but it took months. I have 2 out of 7 issues fixed on WinAppSdk repository and 0 out of 8 issues fixed in the WinUI 3 repository (some of the older than a year). This are just my issues, there are many other opened by other developers. So yeah, it wasn't fun at all. PoweshellSDK had an issue with the Import-Module command and it wasn't fixed for more than a year and probably won't be ever fixed, but I'm glad I found a workaround, even more clean and more safe, otherwise I couldn't have added the posibility to uninstall and change Store apps.
-
Build 23451 includes a better implementation of improved File Explorer tab dragging (you can drag tabs out to create a new window or drag between windows) - still a bit buggy but nice to see anyway!
Compared to UWP or WPF, WinUI 3 is somewhere between 100-200% slower and consumes 7-20 times as much RAM as the old frameworks (for certain operations).
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.
MahApps.Metro - A framework that allows developers to cobble together a better UI for their own WPF applications with minimal effort.
Xamarin.Forms - Xamarin.Forms Official Home
SecureUxTheme - 🎨 A secure boot compatible in-memory UxTheme patcher
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
metroframework-modern-ui - My humble attempt to bring the new Modern UI alias Metro UI of Windows 8 to .NET Windows Forms applications.
FlatLaf - FlatLaf - Swing Look and Feel (with Darcula/IntelliJ themes support)