title: Building an application using WPF, MVVM and Prism
body: <p>We are on our team, studying the possibility of using WPF with Prism.</p>
  
  <p>Our current solution was built using Windows Forms, therefore there are a lot of factors that must be considered and studied before satisfactorily achieve the objectives of this architecture migration.</p>
  
  <p>The MVVM pattern is one of the technologies that are among the new features that are tied to these factors. This pattern uses a quite different concept of that ones that our team currently knows.</p>
  
  <p>We're reading and learning a lot about it, and we couldn't determine whether its use (purely) will be really productive for our purpose: We will create an application that will have a very large number of windows that will use the CRUD (Create, read, update and delete) model. E.g.: customer registration, registration of products, among others.
  We think the use of this pattern can cause rework during the Models definitions, which must be rewritten during the ViewModels definitions.</p>
  
  <p>I wonder if anyone has any experience report or tip that can guide us regarding the use of these technologies.</p>