It's because the browser is caching the app, and your IIS probably doesn't set any cache expiry headers. Here's some info:
http://stackoverflow.com/questions/2281919/expiry-silverlight-xap-file-from-browser-cache-programmatically Chris On 8 September 2011 13:58, Greg Keogh <g...@mira.net> wrote: > 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 I delete all local v2 and v4 ASP.NET temporary files and > restart IIS, now it’s fixed.**** > > ** ** > > So it looks like the problem was on my client side, not on the server > machine side. I’m not sure which step fixed the problem, but it *might* have > been deleting the local temporary files.**** > > ** ** > > Greg**** > > _______________________________________________ > ozsilverlight mailing list > ozsilverlight@ozsilverlight.com > http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight > >
_______________________________________________ ozsilverlight mailing list ozsilverlight@ozsilverlight.com http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
