Hi, I've been battling with this problem for the last 24hrs and it's driving me mad so any help from here would be appreciated.
I'm working on an app that uses the VirtualPathProvider to put together pages based on content from a database so there aren't any actual pages on the site. During testing on the VS.Net server if I just browse to the site I get a directory listing, but then if I request a specific page that I know is within the database it gets delivered correctly. It seem to be that the app doesn't initialise until a page has been called. If I put in a dummy default.aspx page, when you browse to the site (not specifying a page the app appears to initialise correctly and delivers the default.aspx page from the database rather than the dummy from the root. The VPP is configured to intercept all page requests, check to see if in DB and if it is deliver it from DB, otherwise revert back to delivering from the file system and if it isn't there the .net delivers the standard 404 error. This gives me the impression that when you browse to the site the server looks for a default page and then initialises to deliver it and in doing so triggers the VPP that delivers the page from the datababase. So far so good. So in my mind sticking the default.aspx into the root should be enough to get the VPP to initilises, however when I try to run the code on my IIS server, the app just returns the dummy default.aspx not the one provided by the VPP. So the question is, is there any reason why this works on Cassini but not in IIS? -- Cheers, Julian Voelcker Cirencester, United Kingdom =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
