我正在运行Visual Studio 2010中（如管理员），IIS 7的Windows 7 64位系统。 我可以不带调试就好运行ASP.NET网站在IIS 7中，但是当我preSS F5调试它，我得到：

I am running Visual Studio 2010 (as Admin), IIS 7 on Windows 7 x64. I am able to run the ASP.NET web site in IIS 7 without debugging just fine, but when I press F5 to debug it, I get:

无法在Web服务器上启动调试。无法启动ASP.NET调试。更多信息可通过启动该项目没有调试。

Unable to start debugging on the web server. Could not start ASP.NET debugging. More information may be available by starting the project without debugging.

不幸的是，帮助链接是没有帮助我很多，导致下降的东西大树下的心里很不舒服。

Unfortunately the help link is not helping me much and leads down a heck of a large tree of things.

我查了以下内容：

安全性要求 - 我不记得以前有做什么特别的事情。在IIS7的工作进程w3wp.exe的。它说，如果它的运行为ASPNET或网络服务，我必须具备管理员权限进行调试。如何才能知道如果我需要改变这里的东西吗？

Security requirements — I don't recall having to do anything special before. The worker process in IIS7 is w3wp.exe. It says that if it's running as ASPNET or NETWORK SERVICE I must have Administrator privileges to debug it. How do I find out if I need to change something here?

Web站点属性页>启动选项>调试器> ASP.NET检查。 使用自定义服务器设置为站点的URL（其工作正常没有调试）。

Web site Property Pages > Start Options > Debuggers > ASP.NET is checked. Use custom server is set to the URL of the site (which works fine without debugging).

调试在 web.config中启用。

应用程序正在使用ASP.NET 3.5（我想移动到4.0，但最终我有一些迁移处理）。

Application is using ASP.NET 3.5 (I want to move to 4.0 eventually but I have some migration to deal with).

应用程序池：分档.NET程序池（也试过默认应用）

Application pool: Classing .NET AppPool (also tried DefaultAppPool).

任何想法，我可以查下？

Any ideas where I can check next?

当然，它不应该是硬盘安装IIS，VS，建立一个网站，并开始测试它？

Surely it shouldn't be that hard to install IIS, VS, create a web site, and start testing it?

在此先感谢。

推荐答案

原来，罪魁祸首是IIS的 URL重写模块。我已经定义了重定向调用规则的 Default.aspx的（这是设置为启动网站页）到站点的根目录，这样我可以有一个典型的家庭地址。但是，显然VS曾与这个问题，得到了困惑。当我使用赫利的ISAPI_Rewrite因此它甚至没有想到我检查这个问题并没有发生。

Turns out that the culprit was the IIS Url Rewrite module. I had defined a rule that redirected calls to Default.aspx (which was set as the start page of the web site) to the root of the site so that I could have a canonical home URL. However, apparently VS had a problem with this and got confused. This problem did not happen when I was using Helicon ISAPI_Rewrite so it didn't even occur to me to check.

我结束了从头开始创建一个全新的网站，并在一点一点地移植项目/文件到我的解决方案和重建我的web.config，直到我发现了这一点！ 好吧，至少现在我已经使用.NET 4.0（到目前为止，我希望不会碰到任何墙壁）略有更清洁的网站 - ！但什么是痛

I ended up creating a whole new web site from scratch and porting projects/files over little by little into my solution and rebuilding my web.config until I found this out! Well, at least now I have a slightly cleaner site using .NET 4.0 (so far, hopefully I won't run into any walls)--but what a pain!