'The VirtualPathProvider returned a VirtualFile object with VirtualPath set to '/Page.aspx' instead of the expected '//Page.aspx'. '

	The VirtualPathProvider returned a VirtualFile object with VirtualPath set to '/Page.aspx' instead of the expected '//Page.aspx'.
	If you're here because you've just done a Google search for an error like "The VirtualPathProvider returned a VirtualFile object with VirtualPath set to '/Page.aspx' instead of the expected '//Page.aspx'" then I have some good news for you. The reason you get the error is that your virtual page has a compilation error in it. It has nothing to do with your VirtualPathProvider, really. What seems to be happening is that it calls your VirtualPathProvider for your page, gets the appropriate Stream that points to the file's contents, tries to compile the page, fails, and then calls your GetFile () with the same parameter but with an extra '/' at the front. I have no idea why it does this. I'm also sad that Google let me down (there was only one hit and it didn't have an answer) and I had to figure this out for myself. I mean, having to actually think? And I'm embarrassed at how long it took me to figure out... Still, hopefully it'll help someone else out. Categories: .NET Technorati Tags: ASP.NET VirtualPathProvider Permalink #.Posted by 'geoff' on Thursday, 17 May 2007 at 6:26PM <- Previous Blog Post Next Blog Post ->

	Comments, Trackbacks and Pingbacks
	Thanks Thank you, thank you! How did you figure that out, anyway? Posted by 'Star' on Friday, 20 June 2008 at 8:11PM Trial... Trial and - a lot of - error! Posted by 'Geoff' on Saturday, 21 June 2008 at 11:09AM Not quite... Hi, I'm getting that error when I have a website as a virtual directory within another website. If I open the original website and go to the page in question through it's own website it all works fine so there is no compilation error. When I go to the page in question as a virtual directory within another website then I get the above error. Could it be a web.config thing? Cheers, MH Posted by 'Biffster007' on Tuesday, 20 January 2009 at 10:34PM Hard to say Hi, I think it's really hard to say what the underlying problem is. My guess (and it's only a guess) is that there's some exception being thrown when it's in a virtual directory. As you say, it can't be a parse error when it parses OK on another site (unless your references / DLLs in the bin directory are wrong). I'm not sure what to suggest to dig into it further - are there any other relevant messages in the Event Log? Can you attach a debugger and break on exceptions? Good luck, Geoff Posted by 'Geoff Taylor' on Wednesday, 21 January 2009 at 12:01PM

	Post A Comment
	Your Name: Your URL (optional): Comment Title:

View my Technorati Profile.
	Subscribe to the RSS 2.0 feed for Geoff's Blog.