A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More


Apr 27, 2011
  3878
(4 votes)

IMPORTANT: .ASPX file caching/compilation issues caused by my open source assemblies

The Problem

Some of us over the last few months have been experiencing issues within our EPiServer sites where when we have been changing .aspx, .ascx and other files within our web application the changes have not been reflected when viewing the pages in our web browsers.

Today I noticed an issue that was logged against my FilteredPageReference assembly http://episerverfpr.codeplex.com/workitem/list/basic. which pointed at the assembly causing the compilation/caching issues we have been experiencing

The Cause

The search and replace plugin I developed last year uses embedded resources and custom resource path provider classes.  During development I had issues with my ResourcePathProvider class and more specifically the GetCacheDependency method within it.

I was retrieving exceptions when browsing to some of my virtual resources telling me that the folder they lived in didn’t exist.  At the time to resolve the issue I created a cache dependency against the web.config.

Unfortunately the result of this has caused the issues mentioned above.

The Solution

I have updated all of the projects that have been affected by the issue, new versions of the assemblies can be downloaded using the following links:

Sorry Guys and Gals Sad smile

I apologise if this has caused some of you some headaches.  It certainly has caused myself and my colleagues headaches over the last few months.

What more can I say, this is software development and bugs creep in but all should be sorted now!

Apr 27, 2011

Comments

seth@blendinteractive.com
seth@blendinteractive.com Apr 27, 2011 04:45 PM

Thanks for the update and especially being so open about it. Glad to know there is a resolution!

Deane Barker
Deane Barker Apr 27, 2011 04:46 PM

Thanks for this, Lee. It had become a big problem for us. I really appreciate you stepping up and posting the solution.

Erik Nordin Wahlberg
Erik Nordin Wahlberg Apr 27, 2011 04:51 PM

I'm using https://www.coderesort.com/p/epicode/wiki/GoogleAnalyticsAPI which also uses embedded resources via a handler. Wonder if this is the issue in my case... If it is, I will send you some big big love! :)

Apr 28, 2011 08:20 AM

Very well handled Mr Crowe!

Apr 28, 2011 01:21 PM

Yay, its the same issue with the GoogleAnalyticsAPI-code as well...!!

The code should of course check against the virtualPath before handing out the NeverExpiresCacheDependency, just like is done in the other methods...(!)

Good catch!!!

/johan

Please login to comment.
Latest blogs
Building simple Opal tools for product search and content creation

Optimizely Opal tools make it easy for AI agents to call your APIs – in this post we’ll build a small ASP.NET host that exposes two of them: one fo...

Pär Wissmark | Dec 13, 2025 |

CMS Audiences - check all usage

Sometimes you want to check if an Audience from your CMS (former Visitor Group) has been used by which page(and which version of that page) Then yo...

Tuan Anh Hoang | Dec 12, 2025

Data Imports in Optimizely: Part 2 - Query data efficiently

One of the more time consuming parts of an import is looking up data to update. Naively, it is possible to use the PageCriteriaQueryService to quer...

Matt FitzGerald-Chamberlain | Dec 11, 2025 |

Beginner's Guide for Optimizely Backend Developers

Developing with Optimizely (formerly Episerver) requires more than just technical know‑how. It’s about respecting the editor’s perspective, ensurin...

MilosR | Dec 10, 2025