C#•2y ago

Any WPF Guides?

I'm creating desktop website of receipting system using WPF in C# Visual Studio during my internship project.

I searched through various videos on Youtube and most of them are outdated or maybe I'm just confused to follow which one of them because their logic in the code is all different.

I got the grasp the use of XAML and C# OOP, but not MVVM. I even bought some online course in Udemy, but they barely touch or explained the MVVM part. But do feel free to recommend anything that I should learn more about WPF that suits could my project requirements.

Buddy•4/24/24, 3:04 AM

A good way to learn mvvm (at least part of it) is to actually use mvvm libraries, like MVVM Toolkit

Buddy•4/24/24, 3:05 AM

But never use youtube to find quality documentation, prefer articles on the internet.

Buddy•4/24/24, 3:06 AM

https://intellitect.com/blog/getting-started-model-view-viewmodel-mvvm-pattern-using-windows-presentation-framework-wpf/

IntelliTectKevin Bost

Master the Basics of MVVM for Building WPF Applications - IntelliTect

Master the basics of MVVM to simplify the process of building a WPF application & you'll create a more maintainable, easier to unit test app

Buddy•4/24/24, 3:07 AM

https://learn.microsoft.com/en-us/dotnet/architecture/maui/mvvm

Model-View-ViewModel - .NET

Overview of the Model-View-ViewModel pattern used by .NET MAUI

Buddy•4/24/24, 3:10 AM

Also, paid courses are a scam. Don't fall for it.

Buddy•4/24/24, 3:10 AM

Learn by doing

BBuddy But never use youtube to find quality documentation, prefer articles on the inte...

HirankoOP•4/24/24, 3:10 AM

I see, thank you very much :catpog:

Buddy•4/24/24, 3:10 AM

While browsing docs of course.

BBuddy Also, paid courses are a scam. Don't fall for it.

HirankoOP•4/24/24, 3:11 AM

I agree... barely learnt anything from it...

arion•4/24/24, 3:16 AM

Hope I can bring some insight here. I'd recommend that during your exploration that you not use AI assisted coding tools, in many cases during learning they can hurt your experience

To get to mvvm, it's basically a separation of concerns, to prevent spaguettification of code. You don't need your systems so intermingled that you can't see a difference anymore.

View in its basic form is the UI (User interface) or the UI layer (some code that gets used by the UI)

The model is a bit complicated since it encompasses many things but basically it's something that isn't connected to your UI. Ideally it's something like a DTO.

View Model in its basic form connects well, the view and the model. It's the code that makes the model compatible with the UI, most of your app's code should live in these (except of course the XAML)

Try looking at other people's projects that use MVVM and had a lot of stars on their GitHub (I'm hoping that many stars means they use MVVM correctly)

arion•4/24/24, 3:20 AM

Essentially, MVVM ensures that your code can easily be repurposed for other things.