I have two different models that need saving; a TextFile object and a static Settings object.
Right now, I have the save logic implemented in the models themselves.
I like how clean this looks, when calling the save methods:
Settings.Save();
and
_currentFile.Save(filePath);
However, from what I have read it sounds like I am supposed to implement the Save methods in the ViewModel.
Is what I am doing right now improper?
Saving goes in the model. But, it might not go in that particular class (the Model consists of all of your actual workload).
The ViewModel only exists to translate from the Model to the View. It should have no business logic.