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

Popular posts from this blog

Delphi XE2 Indy10 udp client-server interchange using SendBuffer-ReceiveBuffer -

Qt ActiveX WMI QAxBase::dynamicCallHelper: ItemIndex(int): No such property in -

Enable autocomplete or intellisense in Atom editor for PHP -