ASP.NET applications in IIS 7.0 Integrated mode requires configuration changes if they define custom modules or handlers. However, it is still possible to create portable ASP.NET applications that can function in all three environments without configuration changes.

See how at http://mvolo.com/blogs/serverside/archive/2008/04/15/Creating-portable-ASP.NET-applications-that-work-on-IIS-6.0_2C00_-IIS-7.0-Classic_2C00_-and-IIS-7.0-Integrated-modes.aspx.

Thanks,

Mike

The “Request is not available in this context” exception is one of the more common errors you may receive on when moving ASP.NET applications to Integrated mode on IIS 7.0.  This exception happens in your implementation of the Application_Start method in the global.asax file if you attempt to access the HttpContext of the request that started the application.

Learn more about why this happens and how to work around it to start enjoying the benefits of ASP.NET Integrated mode for your application: http://mvolo.com/blogs/serverside/archive/2007/11/10/Integrated-mode-Request-is-not-available-in-this-context-in-Application_5F00_Start.aspx.

During IIS7 development, I've written quite a few modules for IIS7 / ASP.NET.  Some of these were for various demos, others were to help out various internal and external customers, and others just because they were fun to write. 

Now, I am thinking about upgrading some of these with the feature requests and bugfixes you have been asking for, and getting some new ones up as well.  Come check out what you can get right now, and weigh in on what I should next at http://mvolo.com/blogs/serverside/archive/2007/10/28/Mike_2700_s-IIS7-modules-_2D00_-what_2700_s-coming-next.aspx.

You may have noticed mvolo.com being unavailable at certain points over the past two days.  I am in the process of moving the server across the country, and that combined with certain other toubles with the internet setup is contributing to spotty availability.

Next week the server will find its new permanent home so it will start being available 24/7 once again.

In the meantime, sorry for the inconvinience.  Do check back soon as there are A LOT of exciting news and new stuff coming your way next week.

Thanks,

Mike

This article, the first in the IIS7 .NET Developer series, focuses on getting started with developing IIS7 web server features based on the .NET Framework.  Learn about the options you have for your development environment, how to set up your Visual Studio project, when to build a module vs. a handler, and more.  By the end of the article, you would have built and deployed a simple IIS7 managed handler and module.

Read the entire article at http://mvolo.com/blogs/serverside/archive/2007/08/15/Developing-IIS7-web-server-features-with-the-.NET-framework.aspx.

IIS7 configuration extensibility allows you to create custom configuration sections that can be used side by side the IIS configuration sections.  However, setting this up requires a few steps that may be difficult to accomplish, especially in a automated way from a script or an installer.

This post describes the IIS7 configuration extensibility, the steps to create and register your custom configuration sections, and provides a downloadable tool you can use to simplify and automate this process.

Read all about it and download IISSCHEMA.EXE here: http://mvolo.com/blogs/serverside/archive/2007/08/04/IISSCHEMA.EXE-_2D00_-A-tool-to-register-IIS7-configuration-sections.aspx.

If you have worked with IIS6 and previous versions of IIS, you are most likely familiar with the IIS metabase paths.  You know, the ones that look like LM/W3SVC/1/ROOT.  The concept of configuration paths changes significantly in IIS7 with the introduction of the new distributed configuration system, and I wanted to spend some time discussing the new configuration pathsto help you manage and operate your IIS7 server with ease.

Read all about IIS7 configuration paths at http://mvolo.com/blogs/serverside/archive/2007/07/21/Anatomy-of-an-IIS7-configuration-path.aspx.