Ah didn't see this other thread. If you use the last modified time of the xap file then you will download the new version and if its updated then you automatically get the new one, but don't download it every time (which would happen if the url was different on every page load.) you only want the client to download it if the xap file has changed. put the modified date/time in the url and forget about it. move on to more interesting problems. :)
On Thu, Sep 8, 2011 at 12:12 PM, Greg Keogh <g...@mira.net> wrote: > > 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 level (it’s under the IIS – HTTP > Response Headers). I’m not feeling confident.**** > > ** ** > > 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
