Here's the relevant part from web.config we used when running MR in integrated mode on IIS7:
<system.webServer> <validation validateIntegratedModeConfiguration="false" /> <handlers> <clear /> <add name="Trace" path="Trace.axd" verb="*" preCondition="integratedMode" type="System.Web.Handlers.TraceHandler"/> <add name="UrlRoutingHandler" preCondition="integratedMode" verb="*" path="UrlRouting.axd" type="System.Web.HttpForbiddenHandler"/> <add name="MonoRail-Integrated" path="*.castle" verb="*" type="Castle.MonoRail.Framework.MonoRailHttpHandlerFactory, Castle.MonoRail.Framework" modules="ManagedPipelineHandler" scriptProcessor="" resourceType="Unspecified" requireAccess="Script" preCondition="integratedMode,runtimeVersionv2.0" /> <add name="MonoRail-ISAPI-2.0" path="*.castle" verb="*" type="Castle.MonoRail.Framework.MonoRailHttpHandlerFactory, Castle.MonoRail.Framework" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv2.0,bitness32" /> <add name="MonoRail-ISAPI-2.0-64" path="*.castle" verb="*" type="Castle.MonoRail.Framework.MonoRailHttpHandlerFactory, Castle.MonoRail.Framework" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv2.0,bitness64" /> <add name="PageHandlerFactory-Integrated" path="*.aspx" verb="GET,HEAD,POST,DEBUG" type="System.Web.UI.PageHandlerFactory" modules="ManagedPipelineHandler" requireAccess="Script" preCondition="integratedMode" /> <add name="PageHandlerFactory-ISAPI-2.0" path="*.aspx" verb="GET,HEAD,POST,DEBUG" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" requireAccess="Script" preCondition="classicMode,runtimeVersionv2.0,bitness32" /> <add name="PageHandlerFactory-ISAPI-2.0-64" path="*.aspx" verb="GET,HEAD,POST,DEBUG" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll" requireAccess="Script" preCondition="classicMode,runtimeVersionv2.0,bitness64" /> <add name="StaticFile" path="*" verb="*" modules="StaticFileModule,DefaultDocumentModule,DirectoryListingModule" resourceType="Either" requireAccess="Read" /> </handlers> <security> <requestFiltering> <fileExtensions> <add fileExtension=".brail" allowed="false"/> <add fileExtension=".brailjs" allowed="false"/> <add fileExtension=".boo" allowed="false"/> <add fileExtension=".vm" allowed="false"/> </fileExtensions> </requestFiltering> </security> </system.webServer> On Mon, Jan 31, 2011 at 11:52 PM, Brendan Rice <[email protected]> wrote: > After enabling classic mode I found the following article that seems > to have fixed it: > > http://www.west-wind.com/wconnect/weblog/ShowEntry.blog?id=493 > > Thanks for the help guys. > > On Jan 31, 9:46 pm, Patrick Steele <[email protected]> wrote: > > I don't know the technical reasons why Classic Mode works -- but it > > Monorail does run fine in a Class Mode application pool. I'm not > > saying it will fix your problem, but it's a good first step. > > > > --- > > Patrick Steelehttp://weblogs.asp.net/psteele > > > > On Mon, Jan 31, 2011 at 4:26 PM, Tomek Pluskiewicz <[email protected]> > wrote: > > > Why would it be required ot run in Classic mode? > > > > > Also I have noticed that in some cases, MonoRail causes misleading > > > error messages. If I recall right, I have seen 404 in cases where for > > > example Newtonsoft.JSON was missing in deployment. > > > > > I suppose everything was fine in IIS6, but you could try analyzing > > > Server.GetLastError() inside HttpApplication's error handler or log > > > files in case some Exception gets contained inside your application > > > and never really makes it to the yellow screen of death > > > > > On 31 Sty, 02:18, Patrick Steele <[email protected]> wrote: > > >> IIRC, make sure your app pool is running in "Classic mode". > > >> On Jan 30, 2011 7:37 PM, "Brendan Rice" <[email protected]> > wrote: > > > > >> > I developed a site about 3 years ago and am moving the site from > IIS6 > > >> > to IIS7 and am having problems with IIS7 configuration. The version > of > > >> > Monorail that the site runs is 1.0.3.0. > > > > >> > I have mapped monorail to the ashx extension in the httphandlers > > >> > section of the web config as shown below: > > > > >> > <httpHandlers> > > >> > <add verb="*" path="*.ashx" > > >> > type="Castle.MonoRail.Framework.MonoRailHttpHandlerFactory, > > >> > Castle.MonoRail.Framework" /> > > > > >> > When the redirect happens from default.aspx to /home/index.ashx I > get > > >> > the following error message: > > > > >> > The resource cannot be found. > > >> > Description: HTTP 404. The resource you are looking for (or one of > its > > >> > dependencies) could have been removed, had its name changed, or is > > >> > temporarily unavailable. Please review the following URL and make > > >> > sure that it is spelled correctly. > > > > >> > Requested URL: /home/index.ashx > > > > >> > Can anyone help me please? > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Users" group. > To post to this group, send email to [email protected] > . > To unsubscribe from this group, send email to > [email protected]<castle-project-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/castle-project-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.
