+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
I have used this approach too. I actually have a Build.txt in the root of the
application, and set the build number in the web.config and I use:
App.xap?v=2.0.0.1
The query string difference is also enough to invalidate the cache, and it can
be put into the build process easily and only
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
