title: WPF Prism + Existing WPF Application
body: <p>I've an existing application. </p>
  
  <p>With about 3 years of good experience with WPF/MVVM - I feel I should have started with Prism (I've no knowledge of PRISM framework as of now - and I plan to learn it now).</p>
  
  <p>Goals are to -
  - Make the appication a SOLID (design) based framework. Existing code is mix of MVVM (recent new features) and code behind model (existing features)</p>
  
  <p>Since it's a massive application - moving everything to Prism would be quite a task. </p>
  
  <p>Questions:
  - I plan to start a new development (a big feature implementation). Can I use Prism for the new development? I am happy to write most of the components from scratch and slowly go function wise to move entire application to Prism.</p>
  
  <p>e.g. Existing front office real time trading application, planning to add back office/middle office functions to it, and slowly move front office functions to Prism.</p>
  
  <ul>
  <li><p>I have a feeling that learning PRISM can be as much learning curve as it was moving from winforms to WPF - is that true? any suggestions about Books that I should follow? I am a bit of procedural learner and prefer step by step learning from basics (i.e everything about Prism).</p></li>
  <li><p>What are the massive advantages I am going to gain with Prism. Can there be any performance hits at GUI level?</p></li>
  </ul>
  
  <p>Regards, Vinay</p>