This article demonstrates how you can use Visual InterDev 6.0 to do remote Web application debugging on a Web server that is using Site Server 3.0 personalization and membership. This article is geared toward using a server computer with Windows 2000 and Site Server 3.0 with personalization and membership mapping to an Internet Information Services 5.0 (IIS 5.0) Web site, and a client computer with Visual InterDev 6.0....
The Visual InterDev 6.0 debugger may fail under a Terminal Server session. You may experience one of the following symptoms: The debugger skips breakpoints.You cannot see the Mtx.exe (Windows NT), Inetinfo.exe, or Dllhost.exe (Windows 2000) process in the Processes dialog box.Visual InterDev stops responding (crashes)....
This article describes the recommended steps to configure your Web server for remote and local Active Server Pages (ASP) script debugging for use with Visual InterDev 6.0...
In some situations, users want to manually enable Visual InterDev debugging for their Active Server Pages (ASP) applications. In the following scenarios, manual debugging is the only option: Debug an ASP application that is running on a port other than 80. Debug an ASP application that resides on a FAT file system. Debug an ASP application that resides on a virtual server using host header names. Your development computer is not on the same domain as the Web server, or you are not using a d.....
