1. In Browser vs Out of the Browser Nithin Mohan T K nithinmohantk@i-dreamz.org DreamWorkz Technologies http://www.i-dreamz.org

2. Simple Comparison – Part 1 FeatureRIAs in the browserRIAs on the desktop Application deliveryApplications can be easily discovered, explored, and used. Installed applications have more persistence, power, and functionality. InstallationNo application installation is necessary. Applications install seamlessly from the browser or download and install like a traditional desktop application. Application updates Applications are updated by pushing new content to a website. RIA’s provides API’s that allow applications to be updated as easily as pushing new content to a website. Multiple operating system support Applications run on multiple operating systems and browsers. RIA’s are cross-platform, so they can be installed on and run on multiple operating systems.

3. Simple Comparison – Part 2 FeatureRIAs in the browserRIAs on the desktop Background capability RIAs can run only in a visible browser window. Applications can run in the background or provide notifications like traditional desktop applications. PersistenceActivity is limited to the browser session. When the browser is closed, information is lost. RIAs are installed and available on the desktop. They store information locally and operate offline. Desktop integrationApplications are sandboxed, so desktop integration is limited. Applications can access a desktop file system, clipboard, drag and drop events, system tray/notifications, and more.

4. Simple Comparison – Part 3 FeatureRIAs in the browserRIAs on the desktop User interface control RIAs run within a browser window that has its own controls, branding, and integration with the desktop. RIAs have a customizable user interface and desktop integration, enabling branded experiences. Data storageApplications have limited local storage, which the browser can destroy. Applications have unlimited local storage and access to a local database, plus encrypted local storage.

5. Questions?

6. Updates  Silverlight comes with a nice out of the browser experience. So how can we handle updates, if there is an update for the application.  Simple Silverlight provides us a nice API functions to check for the updates.  Such as Invoke updates on click of a button or check for updates on Application startup

7. Updates on Application Startup 1. Open App.xaml file which has application level settings and events 2. On Application_Startup event We need to call the following method this.CheckAndDownloadUpdateAsync();  This Asynchronous function will look for the updates, on the hosted site from where you have installed the Silverlight application on desktop

8. Updates on Application Startup No this is not enough.

9.  Actually this method makes an asynchronous call and downloads the latest update and updates to the current install location.  Note that the current executing application is not yet reflected by the update, we need to restart the application to start using new version.  Here comes the magic of Silverlight  But how do we get notified when update is finished and we can notify the user that a new update is available and he need to restart the application to use the latest application.  In the program we need to attach an Event Handler for CheckAndDownloadUpdateCompleted  see the code snippet

10. This program notifies the user about the status of the update. Go through the screen shots in next steps

11. No updates found

12. Updates found and downloaded After the restart, application will be updated and you can see changes reflected.

13. Few Points…….  Pretty good right, that is the benefit of Rich Internet Applications(RIA), we can push updates from our hosted site. Application does look for an update on each launch.  The sample code I shown is checking for updates on application start up.

14. Few Points…….  Just look through a scenario we need to look for an update only when, user initiates it. Just like clicking on an Update button.  Yes, it is possible. You have to call this.CheckAndDownloadUpdateAsync(); on the click event of the UPDATE button and put an Event Handler to notify about the update. Just like we have done in App.xaml

15.  You could even add some kind of a Background update checker which periodically checks for an Update and notify us about the update.  This is just a beginning more yet to come………… ………………………..  Before 2012….. Just being funny..

16. Questions?