Silverlight .xap needs to be updated in the users’ laptops after pushing a new build

We have pushed so many builds including important bug fixes since July 6. Today our business analysts opened their IE and found out why the bugs were not resolved. I talked to them: Please refresh your IE and make sure if you get the latest .xap file in your laptop.

The interesting part of Silverlight UI is that if users keep their IE open, after we push a new build and they don’t feel that, they can still use the old Silverlight UI. In order to make their individual .xap updated, the best way is to use F12 key to refresh IE, clear browser cache and go to the site again. I showed them how to do it. 

I also talked to them: Please make sure if you can see Silverlight loading progress indicator (1%-100%) every time when you launch IE. This indicates the latest .xap is loaded in your laptop. If not, the .xap might not be updated.



We can also use the following way to see if .xap is updated in our laptop.

Go to %USERPROFILE%\AppData\Local\Microsoft\Windows\Temporary Internet Files\ and you will see sprint2.xap.

Last Modified: It is the time we have the new build (e.g. 7/11/2002 11:24 AM).

Last Accessed and Last Checked: It is the time we access the site (e.g. 7/11/2002 11:43 AM)

 

If your .xap is not updated, please use F12 key to refresh IE, clear browser cache and go to the site again. When Silverlight loading progress indicator appears, everything is working as expected later.