Skip to main content
Support Help Center Help Center home page
AI OnAI Off
Developer documentation Developer community Optimizely Academy Submit a request Sign in
  1. Support Help Center
  2. Optimizely support
  3. Configuration

Page loads slower after updating to .NET 4.7

  • Updated September 12, 2017 20:07

Description

The following issue occurred in Microsoft's 4.7 .NET framework update. 

"The internal implementation of System.Web.Caching.Cache uses Coordinated Universal Time (UTC) time-stamp for absolute expiration. But this particular Cache.Insert (string, object, CacheDependecy, DateTime, TimeSpan) Insert overload method does not make sure whether the expiration time is converted to UTC. Therefore, expiration for items that are inserted into the Cache object by using this overload will occur earlier or later than expected, depending on the computer time zone difference from Greenwich Mean Time (GMT)."

This meant that customers using Cache.Insert could see a higher frequency of database calls since the caching was not used. 

Resolution

Please see the following blog from Quan Mai for a code workaround and for an official fix from Episerver.

http://vimvq1987.com/2017/08/episerver-caching-issue-net-4-7/

You may resolve this issue by updating the CMS Core to 10.10.2 or higher.

Release notes

 

Please sign in to leave a comment.

Articles in this section

  • Configure browser caching in DXC/Azure environment
  • License errors and solutions for Episerver
  • Installing DAM Asset Picker on CMS
  • Setting Up an Alloy Site for CMS 12
  • Configure rewrite rules for CMS 12 applications
  • How to identify license number and other license information
  • Deleted fields still displaying in CMS.
  • The request URL too long
  • Configure NodeJs on DXP Linux (NetCore)
  • Configure maximum upload file size for CMS 12 and DXP Linux platform

See all 58 articles

Optimizely Website Support Policy Privacy Notice Website terms of use Cookie settings Trust center Third-Party Addons & Platforms
Deutsch