4.0 solution with classic application pool?

1 reply. Last post: December 21, 2011 11:12 PM by Martin Lie
Tags :
  • New Discussion
  • New Question
  • New Product Feedback

Hi,

I'm currently migrating some of our projects (with Web UI Studio 2009 R2) to 4.0 and since an entry is required in the <httphandlers> section of the web.config file, this is forcing us to change the application pool of the affected applications to 'ASP.NET v4.0 Classic'.

<httpHandlers>
      <add path="ISRes.axd" verb="GET" type="ISNet.WebUI.WebResourceHandler, ISNet.WebUI, Version=3.0.5000.1, Culture=neutral, PublicKeyToken=b1f2a8511635667a" validate="true"/>
    </httpHandlers>

 

Now... in order to keep working with the default application pool (integrated), what would be advisable? Just adding the key to ignore the integrated mode validation?

<system.webServer>
    <validation validateIntegratedModeConfiguration="false"/>
  </system.webServer>

Or refactor the handler into the system.webserver/handlers section?

<system.webServer>
    <handlers>
      <add name="ISRes.axd_GET" path="ISRes.axd" verb="GET" type="ISNet.WebUI.WebResourceHandler, ISNet.WebUI, Version=3.0.5000.1, Culture=neutral, PublicKeyToken=b1f2a8511635667a" preCondition="integratedMode,runtimeVersionv2.0" />
    </handlers>
  </system.webServer>

 

Regards




All times are GMT -5. The time now is 5:43 PM.
Previous Next