xap

I'm trying to figure out how to force the browser to re-download a .xap file if the new version is available and yet the old one is still cached in the browser. I've seen the other thread: How do you force Firefox to not cache or re-download a Silverlight XAP file? The best solution seems to be: protected void Page_Load(object sender, EventArgs e) { var versionNumber = Assembly.GetExecutingAssembly().GetName().Version.ToString(); this.myApp.Source += "?" + versionNumber; } However, I don't get the this.myApp part. What kind of object is that? I'm sorry for re-opening this, but I wish people

I have a Silverlight control packaged up and deployed to a SharePoint web part. I'm having trouble with the browser loading new versions of the control after I push an update. I'm updating the assembly and file version of my xap project, but it doesn't seem to matter. The only way to get the browser to load the new xap is to go in and delete temporary Internet files. For me, during development, that's OK, but I'll need to find a solution before it's time for production. Any ideas? This has to do with how your browser handles resource requests. Flash has similar issues and there are a couple

We are developing a company app for windows phone 8. I have followed every step described in Company app distribution for Windows Phone Here is what I did: Registered company account Bought an enterprise certificate from Symantec. Exported PFX file with private key Generated Enrollment Token (AETX file) from PFX. Developed application, built with visual studio and get xap file generated. (Name it App.xap) Precompiled managed assemblies and Signed it with certificate using BuildMDILXap.ps1 powershell script. (All messages indicated success). Hosted AETX and signed XAP file on our web server. At

How to do I prevent a Silverlight XAP file being cached by the web browser? The reason I want to do this is during development I don't want to manually clear the browser cache, I'm looking for a programmatic approach server side. Using IIS management add a custom header Cache-Control with the value no-cache . That'll cause the browser to check that any cached version of the XAP is the latest before using it. Add a query parameter to the URL for the XAP in the element on the HTML Page: clientBin/MyApp.xap?rev=1 clientBin/MyApp.xap?rev=2 It will be ignored and break the cache. In IE8, there are