integrated-pipeline-mode

So IIS7 in Integrated Pipeline mode uses a IsapiFilterModule to shim ISAPI filter DLL's and fire off the correct "events" on the filters, which is quite different than previous versions of IIS or IIS7 in classic mode because this means that HttpModules fire off right along side ISAPI filters in Integrated Pipeline mode. So does anyone happen to know how ISAPI events ( http://msdn.microsoft.com/en-us/library/ms524855.aspx ) and the HttpModule events ( http://msdn.microsoft.com/en-us/library/ms998536.aspx ) line up? VMAtm HttpModule events are fired after other filters, according to the MSDN: At

i'm currently having a nightmarish moment with Sitecore. Basically my issues are two-fold: 1) the first time i added a standard value item to a template, and added a layout setup to it, i was thrilled, since all my items from that template were showing the layout, however now, certain items are now showing no layout at all. I tried doing presentation->layout, reset several times, but to no avail. 2) i added a new sublayout to the standard value layout to another placeholder, did publish on the template (republish everything, publish subitems), then publish on the standard values item again,

This is a question that continues to haunt me... In an local Intranet environment, are we doomed to use "Classic" pipeline mode in our App Pool if we want to use Impersonate our Windows domain users, or is there a new way to declaratively "run as" them (so-to-speak)? My goal is to use Windows Authentication for local web applications on my Intranet so users can authenticate and run apps under their active directory account (principle). Every time I try this (Using the NetworkService identity of course), I get this error: Thanks! ;) I wrote a small app to display the current user's network