interdev|visual| Solution | microsoft | Problem Microsoft's article can completely solve the debugging problem of Visual InterDev
You need to install Visual InterDev Server on the second disk of Visual Studio 6.0
Howto:configure Your Web Server for Visual InterDev 6.0 ASP debugging
--------------------------------------------------------------------------------
The information in this article applies to:
Microsoft Visual InterDev, version 6.0
Microsoft Windows NT Server version 4.0
Microsoft Windows NT Workstation version 4.0
Microsoft Windows 2000
--------------------------------------------------------------------------------
SUMMARY
This article describes the recommended steps to configure your WEB server for remote and local Active server Pages (ASP) s Cript debugging for use with Visual InterDev 6.0. There are four basic things that your must do:
Install debugging components on the WEB server.
Add the necessary users to the Administrators group of the WEB server.
Configure DCOM permissions on the WEB server.
Set up a Visual InterDev 6.0 project for debugging.
More information
Install/confirm debugging components on the Web Server
Install or ensure that you are running the following components:
Microsoft Personal WEB Server 4.0 or Internet Information Server 4.0 or later.
Asp.dll version 4.02.0662 or later. If you have version 4.02.0662, the file size must is 330,448 bytes. You can install a updated version of Asp.dll by applying Windows NT Service Pack 4 or later.
You could have to stop WEB services before applying a service pack in order for Asp.dll to get updated. From command prompt, your can type the following to stop Web services:
net stop iisadmin/y
Microsoft FrontPage Server Extensions version 3.0.2.1706 or later.
The Microsoft Visual InterDev Server components. If you don't have a listed in the Add/remove Programs utility in control Panel, can install it by running Setup.exe From the VID_SS directory on Visual Studio CD-ROM 2 or on CD-ROM 1 of the Visual InterDev standalone version.
Remote Machine Debugger components (recommended).
If you don't have a listed in Add/remove Programs, can install it by running Setup.exe from the SCRPT_SS directory On visual Studio Disc 2 or on Disc 1 of the Visual InterDev standalone version.
Visual Studio Service Pack 3 or later, if you are running Windows 2000.
Can download Visual Studio Service Pack 3 from the following location:
Http://msdn.microsoft.com/vstudio/sp/vs6sp3/default.asp
Note:the Web server must be a Windows NT 4.0 workstation/server or a Windows? professional/server/advanced server com Puter.
Add the necessary Users to the local Administrators Group of the Web Server
In order to correctly use debugging, you must is part of the local Administrators group on the WEB server and you'll be Debu Gging against.
Steps to add users to the Administrators group in Windows NT 4.0:
From the Start menu, select Run.
Type:usrmgr Computer name and click OK.
Double-click the Administrators group in the bottom pane.
ADD the users you want to allow to debug.
Steps to add users to the Administrators group in Windows 2000:
From the Start menu, select Programs, and then select Administrative Tools.
From the Administrative Tools menu, select Computer Management.
Expand local Users and Groups under System Tools.
Select the Groups folder.
Double-click the Administrators group in the right pane.
ADD the users you want to allow to debug.
Configure DCOM Permissions on the Web Server
From the Start menu, select Run.
Type Dcomcnfg.exe and click OK.
On the Applications tab, scroll the Catalog Class and double-click it to view Properties.
Select the Security tab.
Click Use custom access permissions and then click Edit.
Add the users that you'll allow to debug to this list, granting them allow Access rights, or simply add the Administrato RS group to this list.
Select The Use custom Launch Permissions option and click Edit.
Add the users that you'll allow to debug to this list, granting them allow Launch rights, or simply add the Administrato RS group to this list.
Sel
