1

I have just deployed a new Silverlight application to several hundred customers. However, many are reporting the same problem - the app looks the same as before - despite massive updates. I've tracked this down to being caused by the Application Storate being stored locally and told my customers to clear this, which inevitably solves their problem.

How can I fix this in future versions ?

I have read this thread on SO which indicates a similar problem, though I don't believe it is the same. I have edited my index.aspx file to have

string strSourceFile = @"ClientBin/MyApp.MyApp.SL.xap?ver=1.2"

rather than

string strSourceFile = @"ClientBin/MyApp.MyApp.SL.xap"

As far as I can tell, there is no way to tell if this change has fixed my problem without deploying again - which I would like to avoid!

How can I test if this has worked/Will this fix my problem?

Thanks very much

Community
  • 1
  • 1
Simon Kiely
  • 5,880
  • 28
  • 94
  • 180

1 Answers1

0

This turned out not to be an issue related to the XAP file, but completely unrelated. It is due to a plugin in use in my SL project - Telerik. I have added serialization tags to new RadPane elements in the xaml file. This does not update correctly in Telerik, the radpanes are maintained in the isolated storage. I have posted a new question with this issue here : Link

Community
  • 1
  • 1
Simon Kiely
  • 5,880
  • 28
  • 94
  • 180