Try our conversational search powered by Generative AI!

Using Virtual Path Providers in EPiServer 4.61



We are using EPiServer 4.61 and we've created an assembly that contains aspx and ascx files as embedded resources, as described in this blog post:

We're trying to call an aspx plugin page in the action window. All that happens is that we get the error:

Exception details: HttpException: The requested resource was not found

Http status: 404 NotFound

Stack trace:

[HttpException: The requested resource was not found]

[Inner exception FileNotFoundException: The file "/core_virtual_path/[assemblyname].dll/[namespace].core.pages.customedit.plugin.[pagename].aspx" was not found]

It seems that whenever we open any other pages, ALL the calls go through the custom made Virtual Path Provider (when we step through the code in the debugger), but when we try to go to the one page that is actually in the virtual path, it never calls the path provider. So I'm guessing that EPiServer somehow tries to look up the virtual path, and since it doesn't exist physically in the web site folder, it throws an exception before the virtual path provider even is loaded.

Does anyone have any ideas what we can do to get this to work?


// Peter

Apr 21, 2008 11:55
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.