Hi Stephen,
Just as a matter of interest, which browser are you using? One of my colleagues was experiencing this but only with Firefox (his IE wasn't working at all for some reason). Regards, Tony From: [email protected] [mailto:[email protected]] On Behalf Of Stephen Price Sent: Thursday, 10 June 2010 4:24 PM To: ozSilverlight Subject: Prism caching dll's Hey all, I've hit a problem on some sites where they appear to be using a proxy of some kind in between the IIS server and their browser. The app is Silverlight 3 and the old versions of the app is being loaded in their browser. It's not detecting that a new xap is available. I tried changing the URL to include the version number which has fixed the problem for the main xap, but as we are using Prism, with each module in its own xap file, all of the modules are also being cached. So the shell gets updated but all of the modules have old content. Clearing the cache on the browser doesn't help as the proxy is just serving them the old xap that it has in its cache rather than realising there is a new one. We have control over the IIS server but not the proxy (some sites don't have a proxy). My question is, is there a way for IIS to tell a particular file type has expired, which will then be honored by a proxy? I've searched but can't seem to find anything that will suit my situation. thanks, Stephen
_______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
