When I replace a .aspx page on my server (shared hosting), I then have to visit the page and wait MINUTES before the page will load. This is really annoying me. I think it's related to the page having to be compiled on the server. Does anyone else experience this problem with their shared hosting?
Does pre-compiling the page take long? Is this the answer?
I've never ever had to wait minutes for an aspx page to recompile. A delay of a few seconds would be acceptable but that seems crazy. I've used a few different hosts and not experienced anything like that.
Is it one particular page that's being problematic, or do you find it with all your aspx files? I'd try to find somewhere else to host it, even if just to test it and see how the same page recompiles elsewhere.
I agree with uretopia - a few seconds at most. If not, sounds like something's up. Maybe the shared server is simply not up to the job... or do you have lots of code in Application_Load or whatever?
To answer your questions, it is not a particular page, it's any page, and the only thing I can think of that could be contributing is the fact that most of my pages also incorporate .ascx user controls, but even then I don't think they are that heavy at all.
Does any one know much of the technical details about how the on server compile works and what can affect it?
wasn't this a .Net 1.1 issue where you published the page and the code file, and then it was compiled the first time it was requested. At .Net 2, the pages are normally pre-compiled locally and then published which gets round the above problem.
Linear Mode
