Home/ Questions/Q 3681906
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-19T03:44:14+00:00

I’m trying to create an silverlight application using the MVVM design pattern. It’s a

  • 0

I’m trying to create an silverlight application using the MVVM design pattern. It’s a kind of bank application.

I’ve watched a lot of tutorials on MVVM but something makes me real confused.

I have about fiwe usercontrols representing my views “TransactionsView”, “AccountView” etc and a bunch of models “UserProfile” – containing user password, username and a list of UserAccounts, “UserAccounts” – containing name, balance and a list of AccountTransactions, “AccountTransactions” – containing a name, and ammount.

Should i create one modelview which contains my userprofile or should i create a viewmodel for every view i have? I’m a doing right so far? Or have i got it completley wrong?

Thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In MVVM, ViewModels are usually 1-to-1 with Views. There isn’t a parity between number of ViewModel and Models, though.

    • View: UI
    • ViewModel: Handles changes to view state, forwarding them to the model if/when appropriate. Sends notifications from the underlying program back to the user. It may also do initial UI validation.
    • Model: Actual “guts” of the application. Algorithms, data storage, system calls etc go here. I put program flow here. I’ve seen other people put it in the ViewModel. That part is up to you to figure out.

    A View always needs a ViewModel, hence 1-to-1 (it could have sub-models, but I’ll leave that up to you to decide on/deal with. I’d start off with 1-to-1).

    A ViewModel usually needs Models to actually “do work”, but how many classes/instances is up to each app/problem you’re trying to solve.

    • 0