ReactiveUI
Avalonia
Our great sponsors
ReactiveUI | Avalonia | |
---|---|---|
18 | 254 | |
7,897 | 23,605 | |
0.6% | 2.2% | |
9.0 | 9.9 | |
5 days ago | 7 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.
ReactiveUI
-
Humble Chronicles: Managing State with Signals
ReactiveUI is based on Rx and very popular in the .Net world: https://www.reactiveui.net/.
-
Source generators run unreliably on VSCode and Rider? (MvvmToolkit)
I use PropertyChanged.Fody all the time and it works fantastically and consistently for implementing INotifyPropertyChange. It is even smart enough to understand dependencies within your get/set functions (should you choose to have custom ones) and notify that property if any of it's dependent properties change. While we are on the subject, if you are using MVVM with observables, you should really check out ReactiveUI. It is wonderful.
- What is a good alternative (or substitute) for MVVMLight?
-
System.Reactive v6.0.0-preview.1 available on NuGet
Personally I learned to use rx and observables by starting to use ReactiveUI combined with DynamicData for my WPF app MVVM architecture. It was maybe not to best choice out there, but I learned to work with it and some things it allows to do is awesome.
-
I want to learn WPF and was told I should use a MVVM based framework any up to date suggestions?
My favorite framework is Reactive UI but it's a bit more advanced than most MVVM frameworks since it uses Reactive Programming. You can still try its most basic features, though.
-
Which GUI framework should I learn: WinForms, WPF, Avalonia or something else?
There is a lot of overlap between WPF and Avalonia so I would start with either one of those. Most certainly Avalonia if you plan to do cross platform dev. I would also highly recommend that you learn and conform to MVVM and dependency injection for your architecture in order to write clean, maintainable, and testable code. My recommendation is ReactiveUI. It leans heavily on more modern patterns like Reactive extensions and IObservable and it can do so much more than just MVVM. As such, it is also very similar to Angular so the concepts will transfer easily if you ever need to do web development. On a side note, Pluralsight has a nice quick course on SOLID design principles. If your code is a mess, it would be a good idea to take a course on this though learning MVVM will be a big step in the right direction.
- Why is there a lack of cool repos?
-
WPF or WinForms
Also, about data binding and reactivity if you really enjoy WinForms, nevar forget!! https://www.reactiveui.net
-
Getting head around {get;set} for C# Models
Your UI needs to bind to something that can programmatically notify it about changes, we call these things View-Models. Usually View-Models implement INotifyPropertyChanged interface (another key interface is INotifyCollectionChanged that is responsible for notifying collection views that number of items is changed and they need to update the UI accordingly). You can do that (the implementation of the interface) manually or use some library to do that for you just to cut some boilerplate code (e.g. ReactiveUI + Fody or Microsoft.Toolkit.MVVM or maybe even this or this).
-
Managing resource files for an app
Some projects like ReactiveUI take on a more webapp style project structure, with resources being in some static resources folder and all code being in a src folder.
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.
- 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]
-
.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.
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?
Prism - Prism is a framework for building loosely coupled, maintainable, and testable XAML applications in WPF, Xamarin Forms, and Uno / Win UI Applications..
Uno Platform - Build Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported.
contact - Retryable HTTP client in Go.
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.
MVVMCross - The .NET MVVM framework for cross-platform solutions, including Android, iOS, MacCatalyst, macOS, tvOS, WPF, WinUI
WPF - WPF is a .NET Core UI framework for building Windows desktop applications.
MVVM Light Toolkit - The main purpose of the toolkit is to accelerate the creation and development of MVVM applications in Xamarin.Android, Xamarin.iOS, Xamarin.Forms, Windows 10 UWP, Windows Presentation Foundation (WPF), Silverlight, Windows Phone.
Eto.Forms - Cross platform GUI framework for desktop and mobile applications in .NET
Caliburn.Micro - A small, yet powerful framework, designed for building applications across all XAML platforms. Its strong support for MV* patterns will enable you to build your solution quickly, without the need to sacrifice code quality or testability.
MahApps.Metro - A framework that allows developers to cobble together a better UI for their own WPF applications with minimal effort.
WPF Application Framework (WAF) - Win Application Framework (WAF) is a lightweight Framework that helps you to create well structured XAML Applications.
Gtk# - Gtk# is a Mono/.NET binding to the cross platform Gtk+ GUI toolkit and the foundation of most GUI apps built with Mono