title: How to optimize loading of a large XAP file
body: <p>We have inherited a silverlight application used in banks. This is a huge silverlight application with a single xap file of 6.5MB size. </p>
  
  <p>Recently one the core banking applications has updated their services to delete the entire browser cache from the users machine on daily basis. </p>
  
  <p>This impacts the silverlight application directly. We cannot afford to download the 6 MB file every day. On a long term basis I know we need to break this monolith in to smaller manageable pieces and load them dynamically. </p>
  
  <p>I wanted to check if there are any short term alternatives. </p>
  
  <ol>
  <li>Can we have the silverlight runtime load the xap in to different director ?</li>
  <li>Will making the application Out of Browser application give us any additional flexibility in terms of where we are loading the xap from ?</li>
  </ol>
  
  <p>Any other suggestions which can help us to give a short term solution will be helpful.</p>