If you need some in-use examples feel free to look around this.
You must be registered to see links
The folder Models is where majority of your code goes.
ViewModels is where ui updates go (more or less).
Thanks alot!
Join our community of MMO enthusiasts and game developers! By registering, you'll gain access to discussions on the latest developments in MMO server files and collaborate with like-minded individuals. Join us today and unlock the potential of MMO server development!
Join Today!If you need some in-use examples feel free to look around this.
You must be registered to see links
The folder Models is where majority of your code goes.
ViewModels is where ui updates go (more or less).
Get out of the habit of writing code in the UI's code behind. Look up MVVM when working with WPF.
It'll save you a lot of headache in the future.
Well writing code that controls the UI itself has to be placed there, but the only thing. No matter you use WPF, Windows.Forms, ASPX, whatever. Always code with a more tier architecture. Split managing logic off the UI. And split data access logic off the managing login.
No, it doesn't. I've halfway through with the program I linked to above, and I haven't written anything at all in the UI's code behind.
Done correctly, you shouldn't have anything at all in that file. If you're altering the ui from that file, you're doing it wrong and you're also opening yourself up to some headaches down the road.
Mostly UI blocking/locked threads.