C # MVC Application on Azure: Site works fine when recently deployed, but fails after being left dormant
I've spent quite a bit of time researching this but haven't found anyone else reporting the issue I have.
I am deploying my site and everything is fine. I share the link with my QA and UI peeps and everything works for them. But if the site goes for a certain period of time, for example, overnight, with no access, the web application cannot start and reports "Method get_CurrentUser" in type ... has no implementation. "Stopping and restarting the site does not solve the problem, but if I just re-upload the main .dll file (the same version of the .dll) to the site then everything works fine, for a while, anyway.
Why would it be nice if it was recently published but couldn't sit down after a while? Any suggestions for troubleshooting this would be greatly appreciated.
source to share
IIS has introduced a Suspend action for idle timeout, when a site is idle for a given duration, IIS suspends the process, god knows what exactly is going on, but it looks like it is just hibernating. And waking up may not work, so you can change this action to stop idle.
The second option is to keep the site up and running using pingdom or site24x7 services.
source to share
Did it help you try the Azure Web app and install Always On? http://azure.microsoft.com/updates/azure-web-sites-adds-always-on/
source to share
Looks like I found a solution.
The application launch event in global.asax includes "var assemblylies = System.Web.Compilation.BuildManager.GetReferencedAssemblies ();" to make sure everything loads, but that line was after the call that started all the dependency registration. I cut / pasted this line to make it happen first, and the site came up well when I tried it this morning.
source to share