try-convert
ReactiveUI
try-convert | ReactiveUI | |
---|---|---|
13 | 19 | |
1,138 | 7,911 | |
0.2% | 0.5% | |
0.0 | 9.0 | |
3 months ago | about 16 hours 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.
try-convert
-
Understanding the .NET ecosystem: The evolution of .NET into .NET 7
dotnet upgrade assistant or dotnet try-convert can help with that.
- dotnet try-convert: https://github.com/dotnet/try-convert
-
converting framework4.8 webapps to NetCore (Net5,6,7). any apps available to help?
try-convert
- Winforms .Net Framework 4.6 Application to .Net 6
-
What shall I upgrade .Net Framework 4.5.2 to for my WinForm project?
Check out https://github.com/dotnet/try-convert
-
I'm used to .NET Framework. Should I try to learn .NET Core?
https://github.com/dotnet/try-convert (usually) makes this a breeze.
-
Moving from .NET Framework to .NET 6
I'm looking to move one of our software suites from .NET Framework 4.7 to .NET 6. A lot of online guides recommend starting with the Microsoft conversion tools to ease/speed up the process. There seem to be two tools that are used for it try-convert and upgrade-assistant. However, I'm not sure I understand the difference between them and when should I use which tool (assuming that it matters).
-
.NET MAUI: Leveraging UIs Across Devices
That would mean you have pretty simple code then, relatively speaking. I helped write the underlying project conversion tool used in the Migration Assistant and found that there's a lot of big and incompatible differences well before you even get into which APIs you're using. Lots of enterprise apps end up using them, whether or not the authors of those apps are aware of it.
-
Advice: Modernizing Old Application Architectures
migrate to SDK-style project files - try-convert does wonders here
-
Help with trying to get a .NetFramework project running in VS2022
Are you using .NET SDK-style projects, or the old scary ones? The latter should load, but since you can't even create them anymore I would expect them to bit rot over time. The try-convert tool should be able to help with that (I wrote most of it, plus the F# support!)
-
Date, Time, and Time Zone Enhancements in .NET 6
there's https://github.com/dotnet/try-convert. Haven't tried it; I instead use https://github.com/hvanbakel/CsprojToVs2017, but I assume the former might be a better choice by now.
ReactiveUI
-
Understanding DynamicData in .NET: Reactive Data Management Made Easy
ReactiveUI Official Website: For information on ReactiveUI, which closely integrates with DynamicData, visit the official website. This site offers extensive documentation and tutorials for both ReactiveUI and DynamicData. 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).
What are some alternatives?
NsDepCop - NsDepCop is a static code analysis tool that helps to enforce namespace dependency rules in C# projects. No more unplanned or unnoticed dependencies in your system.
Prism - Prism is a framework for building loosely coupled, maintainable, and testable XAML applications in WPF, Xamarin Forms, and Uno / Win UI Applications..
CsprojToVs2017 - Tooling for converting pre 2017 project to the new Visual Studio 2017 format.
contact - Retryable HTTP client in Go.
upgrade-assistant - A tool to assist developers in upgrading .NET Framework applications to .NET 6 and beyond
MVVMCross - The .NET MVVM framework for cross-platform solutions, including Android, iOS, MacCatalyst, macOS, tvOS, WPF, WinUI
mpv.net - 🎞 mpv.net is a media player for Windows with a modern GUI.
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.
ClojureDart - Clojure dialect for Flutter and Dart
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.
UWP Community Toolkit - The Windows Community Toolkit is a collection of helpers, extensions, and custom controls. It simplifies and demonstrates common developer tasks building .NET apps with UWP and the Windows App SDK / WinUI 3 for Windows 10 and Windows 11. The toolkit is part of the .NET Foundation.
WPF Application Framework (WAF) - Win Application Framework (WAF) is a lightweight Framework that helps you to create well structured XAML Applications.