By: DotNetKicks.com
IIS 8.0 Application Initialization module in a Windows Azure Web Role… You’ve been kicked (a good thing) – Trackback from DotNetKicks.com…
View ArticleBy: The Morning Brew - Chris Alcock » The Morning Brew #1226
[...] IIS 8.0 Application Initialization module in a Windows Azure Web Role – Sandrino Di Mattia discusses the use of the IIS Application Initialization Module on the Windows Azure Platform, looking at...
View ArticleBy: Dariel Marlow
Excellent post. Everything I needed and nothing I didn’t. Adding your blog to my Google reader.
View ArticleBy: Jason
I am finding that it doesn’t warm up URLs defined in the section on first boot of the VM (w3wp.exe memory usage is tiny and page still takes ages to load). If I stop and restart the web server through...
View ArticleBy: Jason
Got this fixed. A startup task was setting the application pool default value of StartMode to “AlwaysRunning” which was probably firing up the app pool and nullifying the preload.
View ArticleClik here to view.
By: trailmax
Thanks for sharing. But should the IIS Configuration code be withing Start() method, rather than in Run()? If I understand correctly, Run() is for “everyday” tasks, but “Start()” is for config changes.
View ArticleBy: Tom Wilson
Is this the same as app suspend in this post? http://fabriccontroller.net/blog/posts/using-asp-net-app-suspend-in-your-windows-azure-web-roles-os-family-4/ Is app suspend the best way to go now if we...
View ArticleBy: Filip Hurta
I agree, WebRole.OnStart() is better place for this code than WebRole.Run().
View Article