×

First time here?

You are looking at the most recent posts. You may also want to check out older archives. Please leave a comment, ask a question and consider subscribing to the latest posts via RSS or email. Thank you for visiting!

PLEASE READ UPDATE: While the API for checking for updates has changed, the update model *after* that method call to CheckAndDownloadUpdateAsync is the same as described below.  See this note for updates since this article to the Out-of-browser experiences.

Wednesday at MIX09 was a great day.  I was exhausted, but after the keynote I was so high on excitement it was great.  Throughout the day Twitter was buzzing (or is it fizzing?) about all the news around Silverlight 3.  In one conversation around the out-of-browser experiences with Silverlight, I caught a conversation on Twitter about it with questions about the update model.  I jumped in which resulted in this twittersation (sorry, couldn’t resist):

Twitter conversation

So, instead of trying to cram it in 140 characters, I’ll explain here how it works, and take the liberty of using just slightly more than 140 characters.

If you aren’t familiar with the Silverlight Out-of-browser experiences (lovingly referred to as a SLOOB – nod to @bryantlikes), you may want to read my previous post which is a guide to the new features in Silverlight 3 as well as view this video demonstrating the feature.

Detaching the application

The first time your users will view your application it will be in the web context in a page somewhere.  If your application is enabled for out-of-browser (OOB) experiences, then the user can detach the application via a user-initiated action (context menu or some function in your application that calls Detach()).  That process then immediately does a few things:

SLOOB Detach

This action takes the browser (for our example let’s say being served up at http://foo.com/mysloob.xap) and creates an OOB application.  What happens here is the following:

  • The application (XAP) is requested again via the browser
  • The XAP gets stored locally in a low trust location along with metadata which includes the origin URI of the XAP as well as metadata, most importantly for this discussion the ETag information of when it was downloaded (timestamp essentially)

The first OOB launch

Now we are all good.  If we close the application and launch it again from the desktop now we’d initiate a startup of the application:

SLOOB Launch 1

What happens in this instance is basically the application looks at it’s metadata for the origin URI of the XAP and makes a request there with.  It compares the HTTP response data (code and ETag) for comparison.  If the app wasn’t updated, then the app launches and all is well.  In fact inspecting the request it would look something like this for our app:

   1: GET /silverlight/oob/ClientBin/OutOfBrowser.xap HTTP/1.1
   2: If-Modified-Since: Thu, 19 Mar 2009 03:52:35 GMT
   3: User-Agent: Silverlight
   4: Host: timheuer.com
   5: X-P2P-PeerDist: Version=1.0
   6: Accept-Encoding: peerdist
   7:  
   8:  
   9: HTTP/1.1 304 Not Modified
  10: Last-Modified: Thu, 19 Mar 2009 03:52:15 GMT
  11: Accept-Ranges: bytes
  12: ETag: "f2e3a81746a8c91:445"
  13: X-Powered-By: ASP.NET
  14: Date: Thu, 19 Mar 2009 03:55:18 GMT

Notice the HTTP 304 Not Modified response.  No further information is sent and we can see that no content was even delivered.  The app hasn’t changed.  At the API level, Application.Current.ExecutionState is not triggered for a DetachedUpdatesAvailable state change.

Application updated, user launches from desktop

Now let’s update the application and upload to our server.  The next time the user launches the application, the same requests happen:

SLOOB Launch 2

Again, the requests are made sending the metadata information.  In this case though, there is an update.  What happens next is two fold.  Along with the response being sent with a new timestamp/ETag, the request also includes the bits of the updated application.  Looking at the request it would look like:

   1: GET /silverlight/oob/ClientBin/OutOfBrowser.xap HTTP/1.1
   2: If-Modified-Since: Thu, 19 Mar 2009 03:52:35 GMT
   3: User-Agent: Silverlight
   4: Host: timheuer.com
   5: X-P2P-PeerDist: Version=1.0
   6: Accept-Encoding: peerdist
   7:  
   8:  
   9: HTTP/1.1 200 OK
  10: Content-Length: 15557
  11: Content-Type: application/x-silverlight-app
  12: Last-Modified: Thu, 19 Mar 2009 03:56:29 GMT
  13: Accept-Ranges: bytes
  14: ETag: "ce39d0ae46a8c91:445"
  15: X-Powered-By: ASP.NET
  16: Date: Thu, 19 Mar 2009 03:56:45 GMT
  17: <data>

Where “<data>” in the snippet above would actually be the bytes (notice the Content-Length and Content-Type headers) of the updated XAP.  Two things happen now:

  • Application.Current.ExecutionState changes to a DetachedUpdatesAvailable state. 
  • The XAP in the local storage location is updated to the new bits.

Now right now there is no option to decline the updated bits.  If the app is updated, your users will get them.  This is something the team is considering understanding different scenarios.  Also, there is no way to force the user to shutdown the app or prevent them from continuing.  You should build your app in a manner that if an update occurs that perhaps you block the UI until the update is launched.  Re-launching the application (from the local machine) would startup again with the newly downloaded bits and the updated request would look again similar to the first:

   1: GET /silverlight/oob/ClientBin/OutOfBrowser.xap HTTP/1.1
   2: If-Modified-Since: Thu, 19 Mar 2009 03:56:49 GMT
   3: User-Agent: Silverlight
   4: Host: timheuer.com
   5: X-P2P-PeerDist: Version=1.0
   6: Accept-Encoding: peerdist
   7:  
   8:  
   9: HTTP/1.1 304 Not Modified
  10: Last-Modified: Thu, 19 Mar 2009 03:56:29 GMT
  11: Accept-Ranges: bytes
  12: ETag: "ce39d0ae46a8c91:445"
  13: X-Powered-By: ASP.NET
  14: Date: Thu, 19 Mar 2009 03:57:12 GMT

And that’s the basic mechanism of it.  When an application is detached, metadata is stored about that app.  Each launch it does a check against that metadata to see if an update is visible.  If the app is offline, that’s fine, it won’t block the app from launching.  This is very similar to the .NET Framework’s ClickOnce concept in deployment.

Contrast with Adobe AIR Update Framework

Kevin asked me to contrast that with how AIR does it because he felt that “in AIR, very straightforward.”  Now, as you can also see in the initial conversation, I admitted not knowing how AIR worked.  I’m basing the following (and I won’t go deep to get myself into “you’re an idiot” trouble) off of my research in the Adobe AIR developer tutorial on Using the Adobe AIR Update Framework

Now as far as I can tell, first the update framework is not a part of the core AIR runtime and [UPDATE] is avialable in the AIR 1.5 SDK (thanks David for the note) is a separate plugin/module/whatever-term-would-be-appropriate-for-the-runtime for AIR.  Mihai in the tutorial points to needing to download the update framework which apparently is a lab framework (I’m not sure if that means beta, supported or what – if someone knows please comment)?

Once the framework is included the next step is that the developer has to create an update manifest which is described as:

This is a small XML file that keeps information needed by the updater (for example, what version is available, from where to take it, and what info to display). This file sits on your server, and when the application starts up it loads this file to see if any updates are available.

Essentially a file sitting on some location that the app can retrieve (presumably a web server).  The developer then implements an event handler on the AIR WindowApplication.creationComplete event to check for an update.  This includes about 10-15 lines of code to tell the update framework where the manifest file is and to attach to some additional event handlers and code.  When the update is noticed and needed a prompt will occur and AIR has a default UI that would be shown:

Adobe AIR Update Dialog

I like the default UI, it’s informative.  Notice the Release Notes information.  This information comes from the manifest file.  I like that too…good idea.

What it appears to me though is that when the developer has an update the manifest needs to be manually updated or no update events would be triggered.  Perhaps that’s a good thing for granular control over optional events.  I couldn’t find information if you can modify whether “Download Later” was an option or not (thus forcing an update).

Summary

So there you have it.  In Silverlight 3 you have a framework to enable you to auto update your bits.  We’re still in beta so things may change and we know there are questions that you may have on our model (if you have those questions, please leave a comment here).  In AIR you have a framework that doesn’t appear to be a part of the core runtime but that provides the same methods for providing notification to your users.  If I’ve gotten my interpretation of the AIR tutorial wrong, please someone kindly correct me as it wouldn’t have been my intent to do so.

I hope this helps understand the model.  If it didn’t, then perhaps I should have just used 140 characters.


This work is licensed under a Creative Commons Attribution By license.


3/18/2009 10:31 PM | # re: Silverlight 3 Out-of-browser Update Model
The Adobe AIR Update Framework was included in the Adobe AIR SDK with version 1.5 (released last November). It is out of beta.

However, this is just a framework that makes the update process a bit easier. The developer has access to a lower level Updater class that they can use to make the updating process completely customized (so they could use something other than the XML file approach). The developer is also able to utilize a completely customized UI for the update (which you can also do with the updater framework).
3/18/2009 11:57 PM | # re: Silverlight 3 Out-of-browser Update Model
Hi Tim:
Good post.I've learned a lot.

Anyway I have a question about SL2 migration to SL3.

Today i tried to implement this Offline functionality to my old SL2 application.

i added the ExecutionStateChanged event to my old App.xaml.cs

and when i call the Application.Current.Detach() method..i got a runtime

exception.

did i miss sth important to add?

3/19/2009 12:21 AM | # re: Silverlight 3 Out-of-browser Update Model
And i add the
1: <Deployment.ApplicationIdentity>

2: <ApplicationIdentity

3: ShortName="MyTasks"

4: Title="MyTasks -- Get-r-done">

5: <ApplicationIdentity.Blurb>A simple tasks list you can take with you on the go.</ApplicationIdentity.Blurb>

6: <ApplicationIdentity.Icons>

7: <Icon Size="16x16">AppIcons/task16.png</Icon>

8: <Icon Size="32x32">AppIcons/task32.png</Icon>

9: <Icon Size="48x48">AppIcons/task48.png</Icon>

10: <Icon Size="128x128">AppIcons/task128.png</Icon>

11: </ApplicationIdentity.Icons>

12: </ApplicationIdentity>

13: </Deployment.ApplicationIdentity>

3/19/2009 6:32 AM | # re: Silverlight 3 Out-of-browser Update Model
@Tim (or anyone),

Does anyone know how we can get the current Windows user name for an offline application? I used Init params when it was hosted in ASP.NET. I looked through the Application namespace/classes and there doesn't seem to be a propery/method to get the current user.

Workaround: My guess is that you could first launch the web application from ASP.NET and have it store the user name in Isolated Storage and then when the app is detached it would know the user. Technically, the desktop link should be the user's but anyone could really launch it. I really don't want to do this.
Gravatar
3/19/2009 8:29 AM | # re: Silverlight 3 Out-of-browser Update Model
Silverlight as a replacement for both winforms and asp.net apps is our push.

We've learned the hard way over the last 7 years (classic asp, asp.net,...) that web only apps are roughly 2 times more expensive than desktop applications over a 5 year production lifecycle.

3/19/2009 11:36 AM | # re: Silverlight 3 Out-of-browser Update Model
Alled - OOB is a Silverlight 3 feature, not a Silverlight 2 feature.
3/19/2009 11:39 AM | # re: Silverlight 3 Out-of-browser Update Model
Bart - good question. The OOB is still sandboxed so you can't get the user name via any local API call. Your idea of IsoStore is a good work around but does pose the exact issue you mentioned. Can you implement a web service call?
3/19/2009 11:40 AM | # re: Silverlight 3 Out-of-browser Update Model
Gravatar
3/19/2009 12:40 PM | # re: Silverlight 3 Out-of-browser Update Model
Hi Tim,

Are there any plans for allowing SL3 desktop mode apps to step out of the sandbox (with full consent of the user of course) ? Being able to write a more classic type of desktop app with Silverlight (thinking of single user DB apps, connecting to a local database?)

Thanks,

Ian
Gravatar
3/19/2009 12:45 PM | # re: Silverlight 3 Out-of-browser Update Model
To add to my last pcomment, kind of like AIR & SQLite, example at www.insideria.com/.../...erying-a-local-datab.html

Thanks,

Ian
3/19/2009 3:17 PM | # re: Silverlight 3 Out-of-browser Update Model
Ian -- we will be in the sandbox, but are looking at enabling certain types of scenarios. With SL OOB, it is in low trust environment and nothing additional for the user to install/configure, etc.
3/19/2009 3:44 PM | # re: Silverlight 3 Out-of-browser Update Model
I have a really dumb question. Aside from deployment, is there any usefulness here, especially for a data driven app that requires connectivity? And why would I pick this over a WPF application if I needed my app to run as a traditional app? Is it simply to avoid forcing users to download the 200MB framework?
Gravatar
3/19/2009 4:10 PM | # re: Silverlight 3 Out-of-browser Update Model
@Bill, one of my scenarios (enterprise by day, shareware by night :-) is for the type of small business apps, distributed by shareware, traditionally one of the sweet spots for VB Classic/Delphi. Instead of a user potentially having to download the full framework and SQL Server (and possible associated installation issues) they could instead run a SL OOB app with something like SQLite as part of the SL runtime. I think SL + SQLite(or similar) + printing support would be a killer in this area. Huge downloads can be a big competetive problem against a 5mb native .exe application :-)
3/20/2009 8:51 AM | # re: Silverlight 3 Out-of-browser Update Model
soo, when will the sync framework fit!?
3/20/2009 8:58 AM | # re: Silverlight 3 Out-of-browser Update Model
Todd -- third person to ask me that in < 24 hours! I'm checking with Sync framework team to get some ideas on what might be possible here.
3/20/2009 9:34 PM | # re: Silverlight 3 Out-of-browser Update Model
Thanks so much for updating us about Silverlight 3. I have a question:
How about printing in silverlight 3?
Thanks,
Rachida
3/21/2009 12:07 AM | # re: Silverlight 3 Out-of-browser Update Model
Rachida - no direct print of XAML screen support in SL3
3/21/2009 9:20 PM | # re: Silverlight 3 Out-of-browser Update Model
Good information, thank you.
You mentioned "It compares the HTTP response data (code and ETag) for comparison. If the app wasn’t updated, then the app launches and all is well"...What happens if it is unable to connect to the source to make the comparison (offline)? I believe the SL app would still launch in offline mode. Is this correct? thx
3/21/2009 9:39 PM | # re: Silverlight 3 Out-of-browser Update Model
Davce - yes, if there is no connection it will still launch.
3/22/2009 5:24 AM | # re: Silverlight 3 Out-of-browser Update Model
Tim or anyone

Do I understand right,
the out-of-browser function only applies on the main single .xap?
Or does it automatically also track all subsequent dynamically loaded .xap to be stored locally?

About printing, direct printing of XAML screens is not possible. This sounds confusing to me, is there any way to print at all in SL I just did not see?

LocalConnection: is there any chance to get a local windows service talking to a Silverlight browser instance with LocalConnection API? my plan would be to have a local router (on each client, a windows service) that connects with wcf/tcp to the server. This would give a like mixed experience possible, also in this case printing would be possible.
3/22/2009 7:06 AM | # re: Silverlight 3 Out-of-browser Update Model
Christoph - if your app depends on a connection, then it would be fine.
3/23/2009 11:08 AM | # re: Silverlight 3 Out-of-browser Update Model
Sorry to be the 4th person..but what are the possibilities of a silverlight verison of the sync framework? It would be PERFECT for our needs. Are there any show-stopping limitations like p/invokes or sql server CE must haves? Would it be a total waste of time to just resharper the sync framework into a silverlight dll and see what happens?

Thanks!
3/30/2009 11:48 AM | # re: Silverlight 3 Out-of-browser Update Model
Tim or anyone,

Can I Install the OOB Silverlight application for the first time offline using a CD/USB and then update it Online when connected? This is something similar to a hybrid Click Once deployment and using MazeUI tool to point to new source for New Updates....

3/30/2009 11:49 AM | # re: Silverlight 3 Out-of-browser Update Model
Gowtham -- great question! The updates will check based on the original site of origin installation point, so in your description of your scenario, it would be looking for the CD/USB :-)
3/30/2009 4:09 PM | # re: Silverlight 3 Out-of-browser Update Model
Hi Tim,

Why didn't I see automatic update worked? I uploaded a newer version on Windows Azure and launched SL3 App from desktop. Using Fiddler, I didn't see this packet passed out.
1: GET /silverlight/oob/ClientBin/OutOfBrowser.xap HTTP/1.1
2: If-Modified-Since: Thu, 19 Mar 2009 03:52:35 GMT
3: User-Agent: Silverlight
4: Host: timheuer.com
5: X-P2P-PeerDist: Version=1.0
6: Accept-Encoding: peerdist
3/30/2009 8:45 PM | # re: Silverlight 3 Out-of-browser Update Model
Gary -- you wouldn't see that content *literally* (as that was my application) but would see a request to *your* application...i.e., if your app was /foo.xap then you'd see that.
3/31/2009 10:36 AM | # re: Silverlight 3 Out-of-browser Update Model
Thanks Tim. But I did't see such a packet out. What might be the problem?
3/31/2009 10:50 AM | # re: Silverlight 3 Out-of-browser Update Model
Gary -- can you further explain your steps here? You have an app that you've browsed to on a specific URI. You install that app offline. You update that application, re-upload the XAP to the same point of origin. You then launch the desktop (offline) application. At that point, the update should be downloaded and if you re-launch the app it will use the updated version.

We have seen some issues if "localhost" is the name in the URI - due to some browser caching issues. Try using the machine name when browsing/installing/updating.
3/31/2009 11:09 AM | # re: Silverlight 3 Out-of-browser Update Model
Hi Tim,

I did exactly what you mentioned before. The XAP is hosted on Windows Azure actually.
Would you like to take a look?
twitterbeis.cloudapp.net/#/Views/Updates.xaml
3/31/2009 1:24 PM | # re: Silverlight 3 Out-of-browser Update Model
Ok Gary, I've installed your application...you can email me when you have posted an updated XAP to your application and I'll launch it and see what I see (feel free to email me timheuer at microsoft dot com).
3/31/2009 3:23 PM | # re: Silverlight 3 Out-of-browser Update Model
Tim, I think you can use fiddler to catch the update request packet at this moment, right? even though there is no update available.
3/31/2009 3:51 PM | # re: Silverlight 3 Out-of-browser Update Model
Gary -- sure, I just did and here's what I got (indicating no update):
GET /ClientBin/TwitterBEIS_SL3_SLApp.xap HTTP/1.1
If-Modified-Since: Tue, 31 Mar 2009 20:22:20 GMT
User-Agent: Silverlight
Host: twitterbeis.cloudapp.net
X-P2P-PeerDist: Version=1.0
Accept-Encoding: peerdist


HTTP/1.1 304 Not Modified
Last-Modified: Sun, 29 Mar 2009 18:29:26 GMT
Accept-Ranges: bytes
ETag: "0754a9cb0c91:0"
Server: Microsoft-IIS/7.0
X-Powered-By: ASP.NET
Date: Tue, 31 Mar 2009 22:50:41 GMT
3/31/2009 4:17 PM | # re: Silverlight 3 Out-of-browser Update Model
I did more tests. Looks like it might be related some group policy. Tried two domain joined machines, they didn't send out this packet. Tried one workgroup machine, it did. Do you know what GP may impact this?
3/31/2009 4:20 PM | # re: Silverlight 3 Out-of-browser Update Model
Gary - I don't, but would love to help investigate in the event it is a bug. Please email me offline (timheuer at microsoft) and if you could provide any proxy server information that would be helpful.
4/4/2009 3:17 AM | # re: Silverlight 3 Out-of-browser Update Model
Nice article, I have a very basic question, if we don't have SL plugin we then get install exprience in browser, if such SL apps if someone try to execute in non SL env,will it notify user that he/she must have SL runtime installed on machine? I tried this by attaching a out of browser exe of my SL app,It shown me "sllauncher.exe" in attachment and exe target was "C:\Program Files\Microsoft Silverlight\3.0.40307.0\sllauncher.exe" localhost.0,when I tried to execute it on non SL enviornment,it doens not prompt any error and nothing happened, when I put sllauncher.exe in recycle bin, then it prompt me as missing sllauncher.exe
4/5/2009 8:59 AM | # re: Silverlight 3 Out-of-browser Update Model
Vikram -- your methods will fail. The plugin is still required for this to work, the user still has to have Silverlight installed on their machine.
4/15/2009 9:47 AM | # re: Silverlight 3 Out-of-browser Update Model
Hi Tim,

the Silverlight OOB application can also be downloaded to a non-Windows environment (e.g. MAC or Linux) and run. Is this the understanding?

Thx
KL
4/15/2009 12:15 PM | # re: Silverlight 3 Out-of-browser Update Model
Ka - for Mac, yes. For Linux, Moonlight hasn't released their runtime yet that would match the Silverlight 3 implementations.
4/21/2009 9:19 PM | # re: Silverlight 3 Out-of-browser Update Model
Kim - these diagrams are from Balsamiq - timheuer.com/.../...-wireframes-with-balsamiq.aspx
5/1/2009 5:31 PM | # re: Silverlight 3 Out-of-browser Update Model
Hi Tim,

I watched your video tutorial on SL3 OOB apps and I have a question for you re: icons. I added icons to my app and set them as "Content" type resources, and added references to the icons in the AppManifest.xml file. When I detach the app I see my 128x128 icon in the modal install dialog, however when installed the app is still using the default icons. I'm running XP SP2 (SP3 has failed to install everytime I try).
5/1/2009 5:56 PM | # re: Silverlight 3 Out-of-browser Update Model
Brian - this is a known beta issue with the icons.
5/26/2009 4:59 PM | # re: Silverlight 3 Out-of-browser Update Model
Tim, is there any workaround for the sandbox? My app needs to communicate with a desktop scanner via its Win32 API - is there any possible way to do it in SL3 and/or will that be something that is possible in the future?
5/26/2009 5:05 PM | # re: Silverlight 3 Out-of-browser Update Model
Mark - SL3 will not enable you to do this. The future is unknown ;-) - if you need that functionality, consider WPF. Or you could also install a local service that it can communicate with...
5/29/2009 7:54 AM | # re: Silverlight 3 Out-of-browser Update Model
Tim, I'm having trouble too with the out of browser updates. I have deployed to II7 on Windows 2008, and accessing via Vista Home edition. The OOB fails to issue any GET update checks, according to Fiddler. I have tried both using IP address, & server DNS name of II7 host.

The same deployment does detect updates on a MAC and update accordingly. As an aside, on the MAC, the OOB app fails to close properly, leaving the OOB window running. It needs to be forced closed before the OOB app can be re-run.

It's currently hosted at http://hte.webhop.net/httppush. It's a demo showing event driven pushes from a backend java system.

PS. Great work with SL3, really enjoying it.
5/29/2009 10:23 AM | # re: Silverlight 3 Out-of-browser Update Model
Jason -- yeah the beta has been problematic for consistency. Great demo app though! I think the later builds have improved on this feature.
6/1/2009 11:16 AM | # re: Silverlight 3 Out-of-browser Update Model
Hello Tim.
I'm new to SL. My company is going to develop a new product for which the OOB feature is crucial. We are prototyping in both Silverlight and AIR. One of the features we need is the "reverse communication" of the OOB application with the browser it was launched from. Basically I need to launch OOB from a link in a browser (may be a link in a Silverlight application inside the browser). Then the OOB app has to be able to communicate back to the browser some data, which will be displayed inside the browser. I couldn't find any immediate support for that. May be achieved somehow?

Thank you
Armen
6/11/2009 1:09 PM | # re: Silverlight 3 Out-of-browser Update Model
Hi Tim,

If you could still influence the SL3 release, I'd like to log few things:
1) SLLauncher has sunken 3D border, which looks ugly for OOB content.
2) If there a way to close OOB window programmatically? Like Window.Close() in WinForms?
3) Is ClearType still on the release list for SL3? Very much needed, because grey-pixel antialiasing looks extremely ugly for normal business applications.

Thank you in advance
Lex
7/8/2009 12:37 AM | # re: Silverlight 3 Out-of-browser Update Model
Hi Tim,

I have implemented the OOB Feature in my app(SL3).But when i right click and select install it gives the popup asking for the Shortcut and when i click on ok it install's nothing on my desktop nor my start menu.

AppManifest.xml file is as follows.

<Deployment xmlns="schemas.microsoft.com/client/2007/deployment"

xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"

>

<Deployment.Parts>
</Deployment.Parts>

<Deployment.ApplicationIdentity>
<ApplicationIdentity

ShortName="MyApp"

Title="MyApp-Shortcut"><ApplicationIdentity.Blurb>This application is a demostration of OOB Feature of Silverlight.</ApplicationIdentity.Blurb>


<ApplicationIdentity.Icons>

<Icon Size="16x16">Icons/task16.png</Icon>
<Icon Size="32x32">Icons/task32.png</Icon>

<Icon Size="48x48">Icons/task48.png</Icon>
<Icon Size="128x128">Icons/task128.png</Icon>

</ApplicationIdentity.Icons></ApplicationIdentity>


</Deployment.ApplicationIdentity>

</Deployment>

Did i miss something(some reference etc..)?
10/4/2009 2:36 PM | # re: Silverlight 3 Out-of-browser Update Model
It appears that you have to explicitely call Application.Current.CheckAndDownloadUpdateAsync() (ideally from from your app startup event) to get the SL OOB app to check for an update. It sounded like SL was supposed to do this automatically but it definitely wasn't until I added that line of code.
10/4/2009 2:46 PM | # re: Silverlight 3 Out-of-browser Update Model
Tim - yes, this article was written for the Beta -- the update method is still the same, but has to be triggered by the developer first: see other OOB changes: timheuer.com/.../...d-what-is-new-and-changed.aspx
11/4/2009 3:13 AM | # re: Silverlight 3 Out-of-browser Update Model
Hi Tim. I'm asking myself if it's possible to get OOB feature with MEF ? I know that it's not possible with library caching. But how is it with MEF ?

Thanks for this article !
5/20/2010 10:25 AM | # re: Silverlight 3 Out-of-browser Update Model
Hi I am implementing LocalConnection and OOB in my applicaiton and I some time get the error
The Receiver Name is already presen, I catch the exception and display a message, and redirect to error page. But it comes coming and I would not be able to get rid of this. Can you give me some suggestions on this please.
Thanks
6/28/2010 5:10 PM | # re: Silverlight 3 Out-of-browser Update Model
hi Tim,

Is it possible to create a OOB without having to launch the app in a browser first? something that users can double click on the icon or just launch like any regular Windows application?

Thank you

Sesh
8/9/2010 1:50 AM | # re: Silverlight 3 Out-of-browser Update Model
Hi Tim

how to achieve that User can Login when silverlight is loading app??

sorry for my bad english...

if you get the answer, would you plz send an email to me ? plz
9/16/2010 5:55 AM | # re: Silverlight 3 Out-of-browser Update Model
Hi all,

I'm having a problem with elevated trust, signing and OOB updates - I recently bought a certificate and signed my app but now all existing non-signed OOB installs don't download the new signed one... any ideas how I get them to download it?

The full problem is here if anyone can help.
stackoverflow.com/.../silverlight-4-oob-app-wit...
9/27/2010 10:03 AM | # re: Silverlight 3 Out-of-browser Update Model
Hi,
Very useful information in here.
Is it possible to provide the code for Out-Of-Browser setting Update?
Since it is saying Settings found... Converting but it seems to be hanging ;(
If we had the code we may be able to find out what is going wrong plus it would save you time answering questions :)
1/4/2011 6:51 AM | # re: Silverlight 3 Out-of-browser Update Model
i love facebook n with respect from puerto rico

 
Please add 3 and 2 and type the answer here:

DISCLAIMER:

The opinions/content expressed on this blog are provided "ASIS" with no warranties and are my own personal opinions/content (unless otherwise noted) and do not represent my employer's view in any way.