Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Jan 05, 2013 09:19 PM by NickLocke
Dec 22, 2012 08:43 PM|LINK
Dec 23, 2012 07:30 AM|LINK
If the delay is in the initial loading you could try to increase the applicaition pool timeout value.
Jan 05, 2013 09:19 PM|LINK
I've now found some time to have a closer look at this. It's definitely a delay in the initial startup of each web site/service. Reading other threads on here confirms that each site/service will run in its own application pool. Is that a change in .NET
4.5 and/or Azure 2012, or has it always been like that?
The startup delay is definitely a new phenomenon since the move to .NET 4.5 and Azure 2012 - there were no application changes made at the same time.
I still need some help to understand what is happening here and, more importantly, how to stop it.