If you then had a bunch of HTML content to display then life became a little difficult for this class of apps because there was no browser around any more and so HTML display wasn’t possible for out of browser apps until… When Silverlight 3 came along, it was possible to take a Silverlight application out of the browser and you ended up with a situation like this Īnd it’s possible for these applications to run online/offline and to automatically update themselves. Silverlight has a pretty strong interoperability layer between the CLR code running inside the plug-in and the HTML DOM and JavaScript of the surrounding page so you could use Silverlight to exercise some “control” over the hosting HTML/JS and vice versa but HTML was the starting point.Īnd so if you had a bunch of HTML content to display and wanted to mix in a bit of Silverlight then it was fairly clear what your options were until… The HTML was hosting Silverlight rather than the other way around. Instead of making a call to the IIS Server, BeginRetrieve will process, and EndRetrieve will return, a SmoothStreamingAsyncResult that contains a non-null CacheResponse object to be played back by the application instance of SmoothStreamingMediaElement.Īs demonstrated in the sample, EndRetrieve must wait for BeginRetrieve to complete by using the ar.AsyncWaitHandle.WaitOne method, and, similarly, EndPersist should wait for BeginPersist to complete.In the early days of Silverlight, it was fairly easy to understand that Silverlight content would always be rendered inside of a browser window (whether that be IE, Chrome, Firefox or Safari) where it was surrounded by the hosting HTML content and JavaScript. If BeginPersist and EndPersist have previously run successfully, the cache will already have the required data on a new data request. When the data has been successfully parsed and persisted, EndPersist returns true. If there is enough available storage, the data is stored in IsolatedStorage.

The BeginPersist method parses the data returned from the server. The application will then call BeginPersist to cache the data for future use as needed for the off-line scenario.

On the first pass, before the cache has any data, the calls to BeginRetrieve and EndRetrieve return a null CascheResponse object. When an ISmoothStreamingCache object is engaged and a request for data is issued, the Silverlight Smooth Streaming Client will call each of the methods in order: BeginRetrieve, EndRetrieve, BeginPersist, EndPesist.

Silverlight download offline