I've been looking into better dividing up a WPF project. So far, this example has made the most sense to me (MVC style):
Source: https://www.codemag.com/Article/1201061/CODE-Framework-Writing-MVVM-MVC-WPF-Applications
So I'm trying to figiure out best how to divvy up my project in this fasion. It seems that by default in WPF projects for each form a .xaml file is created, then a .cs file (controller?) is nested within it.
Questions:
- Is the .xaml file always going to be the 'view'?
- Is the .xaml.cs file always going to be the 'controller'?
- Since it doesn't appear a 'model' is created by default in the WPF structure, should my steps for setting up project structure be like this:
a.) Separate the .xaml from it's .xaml.cs file.
b.) Put the separated .xaml file in a Views folder
c.) Put the separated .xaml.cs file in a Controllers folder
d.) Create a Models folder
e.) Create new class in Models folder that will be used by the .xaml.cs controller file we put in the controllers folder.
Does this seem accurate? I am trying to structure my code best for an interview, so I'd appreciate any advice.