MVVM with N-Tier -
i'm not sure implementation of project using mvvm, have project structure project separated
- projtitle.ui.wpf
- projtitle.viewmodel
- projtitle.bal
- projtitle.dal
- projtitle.bo
- projtitle.common
bo dataobject , dal deal db, bal data processed dal, , things such as: computation,business rules,simple linq, etc.
i'm not using helper dal, think old fashion way of processing/getting data database.
sometimes, bal kinda redundant simple function helps operation
is implementation not bad practice?
you should implement in following way:
wpf prj: - views - viewmodel & commands - helpers
dal prj: -ef model -services classes
bll: - process dal applying business logic
facade: - allowing talk bll->dal
, facade gonna used commands of viewmodel
Comments
Post a Comment