First of all this post might sound strange since I cannot expose much information about the solution but I will do my best to give a detailed description.
We have a requirement to serve ASP.NET pages from our server component. I went through with VPP since it seems as the best idea for the scenario. We have successfully served ASP.NET pages with code-behind or stand-alone aspx pages. We even themed them, used masterpages and global resources from the file system. The solution recognizes a fixed path as a virtual directory to be served from the server component. (e.g ~/pages/). From there onwards we have other subdirectories depending on which page you want to open: ~/pages/scenario1/page.aspx. All well until I decided to create a base class in a DLL, reference in my site and set the page to inherit from that without using a codefile. The issue is with the internal System.Web.FileChangesMonitor which insists in monitoring changes for that virtual ...
Go to the complete details ...