你在IIS 6承载ASP.NET MVC时丧失功能？如果有，是什么？ [英] Do you lose functionality when hosting ASP.NET MVC on IIS 6? If so, what?

问题描述

作为一个开发团队，我们正在寻找切换到asp.net MVC和我听说过IIS 6不能够支持所有的MVC功能的传言。这是真的？有没有在IIS 7中支持VS IIS 6的功能的任何官方设定？我们是否应该完全避免IIS6上运行它？

As a dev team, we're looking to switch to asp.net MVC and I've heard rumors about IIS 6 not being able to support all of the MVC functionality. Is this true? Is there any official set of functionality supported in IIS 7 vs IIS 6? Should we completely avoid running it on IIS6?

推荐答案

您不松ASP.Net MVC的任何功能;但是，你有两个选择之一。您可以在定义您的网址的一个扩展，这将使你建立的映射。因此，例如：

You do not loose any functionality of ASP.Net MVC; however, you have one of two options. You can either define an extension on your URL's which will allow you to set up mapping. So for example:

www.example.com/books/computer/list

www.example.com/books/computer/list

有可能成为：

www.example.com/books.mvc/computer/list

www.example.com/books.mvc/computer/list

您可以使用任何你想要的，只要你映射到任何ASP.Net扩展。我目前使用的.aspx这意味着我能避免在有扩展名的URL的牺牲改变IIS配置。

You can use any extension you want so long as you map to ASP.Net. I am currently using .aspx which meant I could avoid changing IIS configuration at the sacrifice of having extensionless URLs.

作为使用通配符映射中提到的另一种选择。这样做是路由所有请求ASP.Net。即使对于静态内容请求，如图像。这确实对性能，你将要衡量一个负面影响。有办法解决这个，我相信如把所有的内容在您关闭了外卡映射一个特定的虚拟目录，但我还没有充分挖掘该选项。

The other option as mentioned is using a wild card mapping. What this does is route all requests to ASP.Net. Even requests for static content such as images. This does have a negative effect on performance that you will want to measure. There are ways around this, I believe such as placing all your content in a specific virtual directory that you turn off the wild card mapping for, but I haven't fully explored that option.

这篇关于你在IIS 6承载ASP.NET MVC时丧失功能？如果有，是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！