It was just out of curiosity that I wanted to know if we need to use any MVVM framework as an available third-party version, or we can directly create and define different projects in our application and call them Model, ViewModel and View and also use them according to their definition.
Does the third-party structure provide something additional and can the application mentioned in the previous paragraph be called as compatible with MVVM.
No, you do not need to use a third-party structure, you can just follow the design pattern. You can follow this link to find out more.
http://www.silverlight.net/learn/advanced-techniques/the-mvvm-pattern/using-the-mvvm-pattern-in-silverlight-applications
MVVM, Catel
, , , " MVVM" ( ). ( Linq2Sql), ViewModel - , - , - / .. , , , , - MyProjectData
MyProjectData
, - MVVM-, MVVM . MVVM patern , MVVM.
, MVVM- , / , MVVM; . Prism /, SL WPF (EventAggregator, Navigation framework, commanding ..).
, -
MVVM Vs. PRISM
, . MVVM . MVVM
MVVM