翻到一个15年讨论mvvm的帖子,里面的大部分观点都是把业务处理放到M层,VM只是简单处理V的ui逻辑和聚合M
但是我实际使用下M是个纯粹的实体模型,没有多余逻辑,VM负责ui的简单逻辑和业务逻辑,
现在怀疑自己了,想问一下大家对这个的看法
相关问题
- ObservableCollection in ViewModel is not updated w
- Is it possible to send a List<Object> in MVV
- How to make an element reference a StaticResource
- Get the selected items of a ListView (MVVM, Calibu
- How to include MaterialDesignXamlToolkit to WPF cl
相关文章
- Best way to implement MVVM bindings (View <-> V
- Using LiveData to set visibility of TextView
- app:visibleGone cannot resolve on android Databind
- WPF MVVM two-way updates
- Difference between Set() and RaisePropertyChanged(
- Generating interface implementation at runtime
- MVVM, Confused about ViewModelLocator and DataTemp
- WPF + Castle Windsor + MVVM: Locator-DataContext
按理来说应该是M层,比如DDD就推荐业务在M层,VM还是越简单越好,就算不在M层处理业务,也尽量别在VM里处理,可以另外加一个业务层。不知道你们具体的框架,如果是C/S模式的项目,业务应该写在S端,VM应该属于C端的吧。