I'm sick... I'm seeing things and now I'm cold. So cold.
Two modes in IIS7: ISAPI and Integrated. Hmm... I thought ISAPI was dead. Anyway, integrated allows you to: plug .NET modules directly into the server (and some other stuff I missed before the demo started).
IISCMD exe allows you to determine some info from the command line. [This would work well in a monad script methinks.] The whole demo is about forcing a login for images as well as pages. I didn't even know this was a problem.
Anyway, integrated mode... you need to worry about: runtime changes, performance impact with multiple transitions (selective execution, execution optimization), IHttpModule event ordering (impersonation, authenticated user), configuration (httpRuntime, httpModules, httpHandlers).
Since the runtime is changed so much... you should worry about module runtime ordering. However this has allowed for expanded ASP.NET APIs (like changing request and response headers) or new server variables. Now that ASP.NET is integrated with IIS we now have response filtering, tracing and web events right in IIS7 (through logging?).
Nice demo shows you how you can intercept response filters and replace "images/" with "layout/images". Cool
Apps are easier to manage. Server Configuration (modules, handlers, runtime settings), Features (custom errors *not new*, url authorization, output cache *fast, native*).
Compatibility: ASP.NET 1.0 not supported, worker process will ber isolated and will use a low-privilege account, integrated mode is for ASP.NET 2.0 only and unified server features (?).
Tags: [PDC05]
posted @ Wednesday, September 14, 2005 2:53 PM