MSDN Mag: Enhance Your Apps with the ASP.NET Integrated Pipeline!
At last, my MSDN article about using the ASP.NET Integrated Pipeline is out in MSDN Magazine. This article is all about using existing ASP.NET features and building new ASP.NET modules to improve existing applications.
What's more, I do this without touching a single line of the application itself, which happens to be a PHP application using the IIS 7.0 FastCGI support.
So go read the article for an in-depth look at using the power of ASP.NET Integrated pipeline to add features, improve security, and turbo-charge performance of your applications. Then head over to my blog to learn more about doing this yourself for your apps on IIS 7.0 - starting with building your own modules and handlers.
Article highlights and more at http://mvolo.com/blogs/serverside/archive/2007/12/20/MSDN-Magazine_3A00_-Enhance-Your-Applications-with-ASP.NET-Integrated-Pipeline.aspx.
IIS 7.0 health model published
The IIS 7.0 health model (Windows speak for known diagnostical and failure conditions experienced by software) has just been pubished on TechNet.
The health model is primarily a list of event log events that are raised by various IIS subsystems, including WAS (technically WPAS now, for Windows Process Activation Service), the IIS worker process, Web Publishing Service (W3SVC), etc.
Read more here: http://mvolo.com/blogs/serverside/archive/2007/12/12/IIS-7.0-health-model-published.aspx.
Breaking Changes for ASP.NET 2.0 applications running in Integrated mode on IIS 7.0
ASP.NET 2.0 applications on IIS 7.0 are hosted using the ASP.NET Integrated mode by default. This new mode enables a myriad of exciting scenarios including using super-valuable ASP.NET features like Forms Authentication for your entire Web site, and developing new ASP.NET modules to do things like URL rewriting, authorization, logging, and more at the IIS level.
As you know, with great power comes great responsibility. Similarly, with making ASP.NET applications more powerful in IIS 7.0 comes the responsibility of making sure that existing ASP.NET applications continue to work. This has been a major challenge for us as we re-architected the entire core engine of ASP.NET, and in the end we were highly successful in meeting it.
This post lists the changes in behavior that you may encounter when deploying your ASP.NET applications on IIS 7.0 on Windows Vista SP1 and Windows Server 2008. Read the detailed list of breaking changes at http://mvolo.com/blogs/serverside/archive/2007/12/08/IIS-7.0-Breaking-Changes-ASP.NET-2.0-applications-Integrated-mode.aspx.