Visual Studio 2005中的经典ASP断点问题

I am trying to set a breakpoint in an ASP page that isn't working correctly.

我试图在ASP页面中设置一个无法正常工作的断点。

I am doing this in visual studio 2005 on Windows server 2008.

我在Windows Server 2008上的visual studio 2005中这样做。

Whenever I try to set the breakpoint with the mouse, the IDE opens up a different page and sets a breakpoint somewhere in that page. I don't know why it is doing this.

每当我尝试使用鼠标设置断点时,IDE将打开一个不同的页面并在该页面的某处设置断点。我不知道为什么这样做。

I have better luck setting the breakpoint using F9, but those breakpoints don't get hit, anyway. The breakpoints that are set in the page that visual studio opens automatically are getting hit, but this doesn't help me, because I don't need to debug that page!

我更幸运的是使用F9设置断点,但无论如何这些断点都没有被击中。视觉工作室自动打开的页面中设置的断点正在受到攻击,但这对我没有帮助,因为我不需要调试该页面!

This is my first time debugging classic ASP, so I could use some help.

这是我第一次调试经典ASP,所以我可以使用一些帮助。

Thanks

2 个解决方案

#1

I've just tested debugging of classic ASP in VS 2008 on server 2008 and it works fine. I haven't got VS2005 to test it on that.

我刚刚在服务器2008上测试了VS 2008中的经典ASP调试,它运行正常。我还没有VS2005对它进行测试。

However if memory serves I've seen this problem when the root folder for the web site project (and you are using a web site not a web application project right?) and the Home directory path in the IIS configuration. E.g., the VS solution points to an UNC path whereas the IIS points to a physical drive. In this case VS can't marry up the file path of the script in the ASP process with the file path of source code in the solution.

但是,如果内存服务我在网站项目的根文件夹(并且您使用的网站不是Web应用程序项目吗?)和IIS配置中的主目录路径时看到了这个问题。例如,VS解决方案指向UNC路径,而IIS指向物理驱动器。在这种情况下,VS无法将ASP进程中脚本的文件路径与解决方案中的源代码文件路径结合起来。

#2

In VS.NET: 
project - properties
  configuration properties
     debugging
        - enable ASP debugging
        - enable ASP.NET debugging

In the IIS snap-in: 
  default Website - properties
      home directory tab
         configuration
            app debugging
               - enable ASP server-side script debugging
   Website (the project you want to debug) - properties
      directory tab
         application name: add

Add IIS process account to Debugger Users group: 
   In Computer Management snap-in:
      System Tools
         Local Users and Groups
            Groups
               Debugger Users - properties
                  Add user IWAM_machine-name (the "Launch IIS process account")

Now, to debug in VS.NET: 
   right-click the .asp page that the application should start from
      select "Set as Start Page"