应用程序池模式问题:经典或集成

我有一个使用spring和ext库的Asp 4.0网站应用程序.我已经使用经典应用程序池模式将其部署在IIS 7中，并且可以正常工作.它在集成模式下不起作用.

I have a Asp 4.0 website application that uses spring and ext libraries. I have deployed it in IIS 7 using classic application pool mode and it works. It doesn't work in integrated mode.

我有另一个使用集成应用程序模式在IIS 7中部署的Asp 4.0 silverlight网站应用程序，它可以正常工作.在经典模式下不起作用.

I have another Asp 4.0 silverlight website application that is deployed in IIS 7 using integrated application mode and it works. It doesn't work in classic mode.

我创建了一个新的ASP Web应用程序，它结合了上面的1和2 Web应用程序.它使用Ext.Net，Spring.Net和Silverlight 4.0.在Visual Studio的Web服务器中，当我以调试模式运行它时，它可以完美运行.

I have created a new ASP web application that combines both of the 1 and 2 web applications above. It uses Ext.Net, Spring.Net and Silverlight 4.0. In Visual Studio's web server, when I run it in debug mode, it works perfectly.

当我在IIS 7中部署它时，它不起作用.如何使应用程序以一种模式运行?是否有一个web.config设置可以定义网站的各个部分以在不同的应用程序池模式下运行?

When I deploy it in IIS 7, it doesn't work. How can I make the application run in one mode? Is there a web.config setting that can define the parts of the website to run under a different application pool mode?

我怀疑您[ext]应用程序遇到的问题是由于它处于集成模式，而您没有填充 web.config 正确.查看 Web.config 的Ext.Net Wiki页面.(也就是说，直到不久前我搜索了确切的细节后，我才意识到存在Ext.Net Wiki！)

I suspect that the problem you're having with the [ext] application is due to it being in integrated mode and you not having populated your web.config correctly. Take a look at the Ext.Net wiki page for Web.config. (That said, I didn't realise there was an Ext.Net wiki until I searched to pickup the exact details a moment ago!)

基本上，对于经典"，您需要在< system.web>< httpModules> 和< system.web>< httpHandlers> 下具有配置条目>，而对于IIS7/集成模式，则分别需要在< system.webServer>< modules> 和< system.webServer>< handlers> 下具有配置条目

Basically, for "classic" you need to have configuration entries under <system.web><httpModules> and <system.web><httpHandlers> whereas for IIS7/Integrated mode you need to have configuration entries under <system.webServer><modules> and <system.webServer><handlers> respectively.