FIX: Exception error message when you use a virtual path provider to serve a Web page that has a ScriptManager control: "Directory '<file directory>' does not exist. Failed to start monitoring file changes."
You create and register a virtual path provider to serve pages from a virtual file system for the Microsoft ASP.NET Web application.
There is a ScriptManager control on one virtual Web page within the Web application.
In this scenario, the ScriptManager control still maps the virtual directories to the file system and instructs the FileChangesMonitor object to start to monitor that directory. Additionally, an exception that resembles the following is thrown:
Server Error in '/Site' Application.
Directory '<file directory>' does not exist. Failed to start monitoring file changes. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
You must have the Microsoft .NET Framework 3.5 Service Pack 1 (SP1) installed to apply this hotfix.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about how to use virtual path providers, click the following article number to view the article in the Microsoft Knowledge Base:
910441 How to use virtual path providers to dynamically load and compile content from virtual paths in ASP.NET 2.0