Browser cache after weekly nuget package update

Hello,

every time we update the Syncfusion nuget package after a weekly release, we are experiencing user problems in the browser. Users are not automatically seeing the newest version, because the old js files are heavily cached in the browser. The only way to solve this, is clearing temporary files in the browser, but we cannot ask this to all our users each week.

The js files should be forced loaded with each new release. This can easily be done be including a version number in the url of the added js includes.

1 Reply 1 reply marked as answer

JA Jesus Arockia Sankaran S Syncfusion Team September 15, 2020 11:48 AM UTC

Hi Davy,  
  
Sorry for the delay. 
  
We have validated your query related to the browser cache and the issue can be to reproduce in the Blazor WebAssembly application.  
  
We would like to let you know that, the static webassets will always be cached in the browser when we using Blazor WebAssembly application since the resources are loaded in the browser side for rendering. 
  
So, we suggest you to set the HTTP header with no-cache option in your server configuration to resolve this problem. Please refer to the below Github thread and ASP.NET forum for more details. 
  
  
 
 
Note: Once you configured, please clear the browser cache then run the app. after that you didn't need to force cache clear 
 
Regards, 
Jesus Arockia Sankaran S 


Marked as answer
Loader.
Up arrow icon