Im posting this up for discussion, advice and any thoughts really.
I have been developing some silverlight components and applications for a while now and a problem that is becoming more prevalent is not being to roll out updated versions of my XAP files to the clients. The reason for the problem is that the Browsers are caching the XAP files, so if I drop a new version on the server this is not being picked up by the clients.
I have looked at a number of recommendations including:-
I have been developing some silverlight components and applications for a while now and a problem that is becoming more prevalent is not being to roll out updated versions of my XAP files to the clients. The reason for the problem is that the Browsers are caching the XAP files, so if I drop a new version on the server this is not being picked up by the clients.
I have looked at a number of recommendations including:-
- Using Query String parameters on the source of the xap file
This will only work if you are using absolute Uri's and if you are not using the asp:silverlight asp.net control to set the parameters - Using a custom HTTP Handler to stream the zap file to the client
Then I have full control, but this just does not feel right. - Tell IIS not to cache the page/control
The problem with this while it will give the updated XAP file you lose the benefit of already having the XAP on the client, as they have to download this everytime.
Well thats where I am at the moment, and short of writing something into my controls to check something on the server etc Im not really sure where to go with this.
Has anyone else experienced this, how did you get round it, what does Telerik recommend as a good approach for this.
As always your help and advice would be much appreciated
Greg