UpdateType = UpdateTypes.ElevationRequired If (e.Error is PlatformNotSupportedException) Update5: As requested, here is my code, fairly straightforward: private void CheckAndDownloadUpdateCompleted(object sender, e) Update4: In fact, the problem is still present even on my main IIS deployment, and has happened on other servers too (and using PHP to generate the timestamp instead of ASP.NET). But this is still annoying, as it considerably slows down my OOB debug process. The same application deployed to a proper IIS with the same Web.config doesn't have this issue. Update3: The problem is definitely related to the debug web server. Now the in browser app detects that the OOB install is ok, but the update cycle continues, with the same Fiddler trace. Update2: I had a cache control directive in my Web.config file, but removing it only solved half the problem. That's fine for me, except that the server (Server: ASP.NET Development Server/10.0.0.0, X-AspNet-Version: 9) returns a new version, with the following cache headers: HTTP/1.1 200 OKĮach time I run the app, the check request has the right date (the one previously returned by the server), and each time, the server says it has a new version, with the current date. When the update process is invoked, I see: GET /ClientBin/Client.xap?timestamp=23%2f01%2f2012+17%3a42%3a14 HTTP/1.1 Update: I've checked with Fiddler what happens on my dev box. The problem occurs on (at least) my dev machine using the Silverlight 5 Developer Runtime. * Precision: currently my app is built using the Silverlight 5 Tools, but is targeting Silverlight 4, and works fine on a Silverlight 4 Developer Runtime. Has anyone else encountered this, and better yet, has a workaround?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |