Upgrades and XAP library caching

3 posts, 1 answers
  1. ewart
    ewart avatar
    221 posts
    Member since:
    Jan 2007

    Posted 21 Sep 2010 Link to this post

    I recently updated my Telerik library to the newest version and ran into a problem, an

    Could not load file or assembly 'Telerik.Windows.Controls.DataVisualization, Version=2010.2.812.1040, Culture=neutral, PublicKeyToken=5803cfa389c90ce7' or one of its dependencies. The requested assembly version conflicts with what is already bound in the app domain or specified in the manifest. (Exception from HRESULT: 0x80131053)

    The library caching still has my old version on my machine it would seem.. however, clearing the browser repeatedly cache definitely does not work.  I think maybe microsoft have been too clever in the caching somehow?

    Even if clearing the cache worked it's terrible solution for usability - basically the app crashes or hangs for existing customers who then bugger off looking for an alternative..  and I can hardly ask or expect users to wipe out their cache every time I do a library update.  

    How can I force a refresh the library download?

    (btw my .xap is called with the parameter like below, using the file's date to force a refresh if it changes, which seems to work great
    <param value="/ClientBin/FitMapper.xap?ignore=9/20/2010 9:02:05 PM" name="source"><param value="ipaddress=" name="initParams">)

    Kind Regards

    I phoned a
  2. Answer
    Valeri Hristov
    Valeri Hristov avatar
    2252 posts

    Posted 21 Sep 2010 Link to this post

    Hi Ewart,

    I am surprised that the assembly caching does not work. We never experienced such problems on our online demos. I suppose that you already checked that, but in any case, could you double check that the Telerik assemblies were properly upgraded and deployed on the server? Usually the compiler does not complain if you mix the assembly versions of the referenced Telerik assemblies, but in runtime exceptions are thrown.

    I experimented with modifying the extmap.xml files - tried to include the version number in the downloadUri attribute, but unfortunately this didn't work. You could experiment with this approach.

    Another idea that just came to my mind is to deploy the XAP and ZIP files to a folder, named after the application version (or the date). This way the ZIP files will be automatically referenced to the relative path, containing the version/date and the cache should work. To avoid keeping many folders you could rewrite the requests to the versioned folders.

    Valeri Hristov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. ewart
    ewart avatar
    221 posts
    Member since:
    Jan 2007

    Posted 16 May 2011 Link to this post

    Incase anyone else has this, (as I'm still experiencing this problem), I can confirm that creating a subfolder with the files everytime you deploy a xap is the solution, quite annoying to have to do, but it works.   I'm not sure if it's relevant but I'm using an internal build version of the RadControls.

Back to Top