I’ve decided enough is enough and I want to leave my comfort zone and finally get away from winforms. Now, before you all flame me, I’ve used winforms strictly for businesses processes. These small apps are internal applications that require rapid development and windows is the only platform that we use. I have a couple of side projects in my head and I want to start designing visually appealing apps.
That being said, I’ve purchase a class on Udemy to give me a basic understanding of WPF but I wasn’t sure what framework to choose. Should I only use NET 5 at this point ?
Yes go with .NET 5. It’s the only sensible way forward.
Unless you have Framework dependencies, go with 5.
You can’t go wrong with either Framework or .Net 5. What matters is if you want to go with the latest performance improvements, new BCL and C# features, or if you want to keep the application as small as possible.
With .net 5 you can’t gurantee that it’s installed on the user’s computer, thus it’s recommended to deploy your application with .net 5 baked in. It’s a 100 MB increase in size. On the other hand, a stray Windows update won’t change behavior in your application because it’s completely decoupled from the OS.
Wait for MAUI if you can afford to wait until Dec 2021 when .NET 6 will come out along with MAUI and Blazor AOT. Microsoft is also obviously absorbing Blazor into Desktop segment, so if they prioritize Blazor over anything else in 2022, XAML may not even have a long future. The world is moving so fast right now. MVVM was a cool productive thing for UI, and now everyone is going with Reactive/Redux approach. Google starts to favor reactive Compose UI for Android, possibly to replace the aged MVP-based UI, and Apple too is trying to push SwiftUI/Combine to replace the aged MVP/MVVM UI frameworks.
and now everyone is going with Reactive/Redux approach.
What do you mean by this? What is the difference between Reactive/Redux and MVVM?
C# devs
null reference exceptions