In 2004, I posted to a couple of forums regarding an exception I was receiving for a website that I maintained. Going back and reviewing those posts made me realize that all I needed to do was read the content of the exception message (blush) and realize that the exception was being generated because the file was not found. Here's an idea of what the message looked like...
Message: c:\someDirectory\anotherDir\webFolder\SomePage.aspx TargetSite: System.Web.UI.ParserCacheItem GetParserCacheItem() Source: System.Web Stack Trace: at System.Web.UI.TemplateParser.GetParserCacheItem() at System.Web.UI.TemplateControlParser.CompileAndGetParserCacheItem(String virtualPath, String inputFile, HttpContext context) at System.Web.UI.TemplateControlParser.GetCompiledInstance(String virtualPath, String inputFile, HttpContext context) at System.Web.UI.PageParser.GetCompiledPageInstanceInternal...
The problem was that the file wasn't found and so never loaded. Unfortunately, I expected to receive a 404 message instead of this GetParserCacheItem Exception. I didn't accept the fact that the file was NOT in the directory, biggest example of why one should RTFM, or in this instance RTFEM. Live and learn...
-Brian
Thursday, October 13, 2005
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment