title: Interface Architecture for Silverlight App
body: <p>I'm getting ready to develop my first Silverlight app.  It is going to be primarily used by my church for data input but also will need to generate at least one report, ideally in Excel but XML/XSLT is not outside the realm...</p>
  
  <p>It will be Internet facing and will talk to a SQL Server 2008 db for which I will be creating a web service hosted at the ISP (db is also hosted at the ISP).  The clients will be a mix of Windows and Mac.</p>
  
  <p>My question specifically relates to the interface architecture.  I know MVVM is big for this right now and I'm comfortable with that.  I want to get this up fairly quickly (ie- next 3-4 weeks).  I've also seen mention of Prism (Composite Application Guidance) and Caliburn.  What are anyone's thoughts on these two?  The initial version of the app is not going to be huge so I don't imagine it would be overly difficult to refactor a framework into it at a later date.</p>