Rapidly iterating Silverlight development

My current default browser is Chrome (dev). I'm using VS2010 and Silverlight4, with ASP.NET MVC3. I don't seem to have the problems with debugging that I've seen others have. My main complaint is that I regul开发者_如何学运维arly have to clear my browser cache to get the latest version of my app to show up. Sometimes I have to clear it two or three times. I've taken to changing the background color of certain elements just to be sure whether I've got the actual latest changes.

Are Firefox or IE better in this regard? Is there are trick to make my latest version always appear?

---

Too lazy to do fiddler.

Seems I hadn't googled very well before, this article seems to be precisely what I wanted http://codeblog.larsholm.net/2010/02/avoid-incorrect-caching-of-silverlight-xap-file

via this discussion which has other options and some useful discussion https://betaforums.silverlight.net/forums/p/11995/449355.aspx

Unfortunately, that part of my project has been on hold for a bit, so I haven't tried it out yet.

---

Like you, I use Chrome for my main browser, and I don't use IE for any regular browsing. But I do use IE for Silverlight development, for this reason and others. I rarely if ever have trouble with the IE cache holding onto outdated versions of my XAP file, but this happens pretty regularly with FireFox and Chrome. In addition, depending on how I closed my previous debug session, when I start up a new one, FireFox and Chrome frequently open up my previous tab(s) in addition to the one that I'm actually trying to debug. Consequently, IE is (for me) the cleanest browser to actually debug with.

This isn't really an answer -- just an observation. Sorry :-).

---

Have you tried investigating why this is happening using Fiddler or a similar HTTP debugging tool? Personally I've never been able to debug Silverlight in Chrome so I usually have to force IE when debugging. But I never have the problem of a stale application. I'd check Fiddler to see if you can isolate the issue. It's probably not directly related to Silverlight.

---

Your probleme looks like a lot like a cache configuration issue. The web server is often configurated rather aggressively concerning caching of static files, as the XAP.

So the response header are probably set in a way that maximize browser caching.

You could change the webserver configuration to prevent client side caching of the XAP file.

Don't forget to remove these setting in production, however.