title: ExtJS Architecture for Multi Page Application
body: <p>I have a .NET application in which most of the UI is custom.  On some of the pages, I am using ExtJS4 components, such as Grid, to display a table of Users for example.  I also have another page where I display a user profile, and another page where I display an application form.  There are many other pages that don't use ExtJS.  I sparingly use ExtJS components and would like to have re-usable code for Stores and Models across all the pages where I use ExtJS.</p>
  
  <p>I am familiar with ExtJS MVC architecture but all the documentation and examples demonstrate best practices for a single page ExtJS app.</p>
  
  <p>For my scenario, I was looking for advice on what the best way to architect the ExtJS code is.</p>
  
  <p>Should I just create the Stores and Models in a common JavaScript file and include that file on every page?  Then create an instance of the Ext.Application or Ext.onReady for every page I would like to use ExtJS components?  Or should I essentially be using a MVC architecture for each page in question just for a few components?</p>
  
  <p>I just want to avoid copy/pasting code and have re-usability.  Please recommend the best path to take.</p>