Question : Running Silverlight 3.0 Out of Browser

I'm new to SilverLight and web programming in general, but I need to analyze the value of creating our application one time, for Windows and web, rather than twice, like we do now.  We have a WinForms application (.NET Framework 3.5) and a web version (also 3.5 ASP.NET) which do the same things and satisfy the exact same requirements, but take double the work and double the time and effort to test them.  So there's a sincere effort to analyze whether we can write once and use twice with SilverLight/Windows WPF or SilverLight/Windows (OutOfBrowser).

I am most interested in learning about the OutOfBrowser mode.  We use SQL Express for the Windows version but SQL Server for the web version.  

Please share with me your experience or understanding about what's involved with running on Windows OutOfBrowser.  I learned it runs in a 32 MB sandbox for security purposes, so to access our local database there would  be a distinct communications protocol needed.  WCF comes to mind as a way to solve this problem.  We do not need to support Windows 2000 on the Windows version (OutOfBrowser version), but need to support Windows 2000 when running the web version, which requires us to use Internet Explorer 6.0.

As far as I know those are our only hard constraints, so please let me know if you have any ideas or experience about running SilverLight 3.0 OutOfBrowser.


Thanks,
newbieweb

Answer : Running Silverlight 3.0 Out of Browser

Pointer to this MSDN Magazine (June 2009 issue) article about Silverlight 3.0 out-of-browser apps, if you haven't see that yet
http://msdn.microsoft.com/en-us/magazine/dd882515.aspx