title: Tips on designing a .Net framework application
body: <p>Can you please provide me with some tips/guidelines when architecting, designing and implementing a .net framework application, with the requirements given below:</p>
  
  <ol>
  <li>It will be an analytical tool which will retrieve data from files, sql databases and may be cubes.  So data layer should be able to handle that.  The middleware should be totally independent of the other layers so probably need an IoC container (which one would you recommend)</li>
  <li>It will be deployed on the local intranet</li>
  <li>The front layer might be WPF application or Silverlight in future (for now, I am concentrating on Silverlight but the point is that it will change)</li>
  <li>It should be easy to customise and improve it in the future without changing much of the code as the framework will be deployed for many clients</li>
  <li>I need a way to store the configuration information, which will be picked up by the application on application load events to set its feel and look.</li>
  </ol>
  
  <p>I have two months to implement it and looking for as many tips as possible.</p>