Made for educational purposes Asp.Net MVC restaurant app.
Functional: receiving food, writing off products, selling dishes (writing off products based on recipes of sold dishes), transferring products between restaurants.
Now I want to try to make on the existing model a WPF application and later a SPA on Angular.
I decided to make a Web API so that all three clients access the database through it. Experience writing Api before this was not.
If I redo the MVC application, do I have to write the API address somewhere in the settings? In controllers, I will call API methods, get json, generate based on its viewModel and send it to view?
Another idea is to make the viewModel classes for MVC and WPF common. Also make some kind of library for wrapping APi methods or is it better to make one class to call all methods to add dependency injection to MVC?
In the right direction I think?
ICommandinterface, to display changing properties in the UI, you will need the implementation ofINotifyPropertyChanged. So such an idea of creating common view models for WPF and MVC is hardly reasonable. - Bulson