+1 to Stephen
I found this in my blog post draft folder
body
form id=form1 runat=server style=height:100%
div id=silverlightControlHost
object data=data:application/x-silverlight-2,
type=application/x-silverlight-2 width=100% height=100%
%
const string
...@ozsilverlight.com] On Behalf Of Simon Hammer
Sent: Thursday, 8 September 2011 12:07 PM
To: ozSilverlight
Subject: RE: Refreshing an SL4 app (client problem?)
Hi Greg,
Funny, I was dealing with this today
We handle this by having a version number in the xap filename (eg.
SLAppName1.5.2.xap
A lazy way to avoid this is to always rename the xap file each version.
Alternatively, In IIS you can specify the no-cache header for the xap file,
however that means that it is always downloaded even when you would prefer
the user gets a cached one (from either their browser cache, asp.net
Folks, I have this random problem where I xcopy deploy all of my app files
over to my Win2008 server box and the updated SL4 app doesn't appear, I get
the previous version.
I have spent hours over the previous months trying to figure this problem
out. I restart IIS, I even reboot, I delete the
Well I should have asked my cat, because I browsed to the SL4 app from the
outside world and it was the latest version. When browsing from my work
machine I see the old version. So I restart my localhost IIS and delete
temporary files in the browser, but it makes no difference. As an
administrator
http://stackoverflow.com/questions/2281919/expiry-silverlight-xap-file-from-
browser-cache-programmatically
Interesting ... some solutions are browser specific, some need code and
maintenance. Adding the Cache-Control: no-cache header seems the easiest
by far, so I'll try it out at the app
hehe, re-read your email and you did say it was SL4 app, so yeah, its
probably what I said. :)
On Thu, Sep 8, 2011 at 1:09 PM, Stephen Price step...@littlevoices.comwrote:
sounds like it may be the client machine caching the xap file.
If that is your problem, if you clear the cache on the