You do not find any script running in the Processes dialog box when you debug an ASP Web page in Visual Studio 6.0 (837316)


The information in this article applies to:

  • Microsoft Visual Studio, Professional Edition 6.0
  • Microsoft Visual Studio, Enterprise Edition 6.0
  • Microsoft Visual Studio .NET (2002), Professional Edition
  • Microsoft Visual Studio .NET (2002), Enterprise Architect Edition
  • Microsoft Visual Studio .NET (2002), Enterprise Developer Edition
  • Microsoft Visual Studio .NET (2002), Academic Edition
  • Microsoft Visual Studio .NET (2003), Professional Edition
  • Microsoft Visual Studio .NET (2003), Enterprise Architect Edition
  • Microsoft Visual Studio .NET (2003), Enterprise Developer Edition
  • Microsoft Visual Studio .NET (2003), Academic Edition

SYMPTOMS

When you debug an ASP Web page in Microsoft Visual Interdev 6.0, and you click Processes on the Debug menu, you may not find any script running under the following processes in the Processes dialog box:
  • Iexplorer.exe
  • Dllhost.exe
  • Inetinfo.exe

CAUSE

When you install Microsoft Visual InterDev 6.0 after you install Microsoft Visual Studio .NET, an older version of the Pdm.dll file is copied in the system32 folder. Therefore, when you browse to the ASP Web page in Microsoft Internet Explorer, the processes that are mentioned in the "Symptoms" section load an older version of the Pdm.dll file.

RESOLUTION

Copy the latest version of the Pdm.dll file from the C:\Program Files\Common Files\Microsoft Shared\VS7Debug folder to the %WINDIR%\system32 folder on your computer.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to reproduce the behavior

  1. Click Start, and then click Run.
  2. In the the Run dialog box, type notepad in the Open box.
  3. Paste the following code in Notepad:
    <html>
<head>
<title>VBScript debugging</title>
</head>
<script runat=server language=vbscript>
Function DoSomething
	dim x,y,f
	x = 3			   
	y = x * 2          
	f = Factorial(y)   
	response.write "The value of f is " + Cstr(f)
End Function 

Function Factorial(n)
	if n = 1 then
		Factorial = 1 'when factorial starts to be returned.
	else
		Factorial = n * Factorial(n - 1) ' Still call next factorial
	end if
End Function 
</script>
<body>
This page contains VBScript.
<br> 
<% DoSomething() %>
</body>
</html>
  4. On the File menu, click Save. You receive the Save As dialog box.
  5. Save the file as test.asp, in the c:\inetpub\wwwroot folder of your computer.
  6. In Microsoft Internet Explorer, type http://localhost/test.asp in the Address bar.
  7. Click Go. You receive the following text in the browser window:This page contains VBScript. The value of f is 720
  8. Click Start, and then point to All Programs.
  9. Point to Microsoft Visual Studio 6.0, and then click Microsoft Visual InterDev 6.0.
  10. In the New Project dialog box, click Cancel.
  11. On the Debug menu, click Processes. You see the behavior that is mentioned in the "Symptoms" section.

    Note In the Processes dialog box, you cannot find the word "Script" under the Languages column.

REFERENCES

For more information, visit the following Microsoft Developer Network (MSDN) Web sites:

IIS request processing
http://msdn.microsoft.com/library/en-us/iissdk/iis/iisrequestprocessing.asp

Error: Unable to start debugging on the Web server
http://msdn.microsoft.com/library/en-us/vsdebug/html/vxtbsHTTPServerErrors.asp

How to enable remote debugging on Windows XP Service Pack 2
http://www.microsoft.com/indonesia/msdn/xpsp2remotedebug.asp

Debugging client-side scripts
http://msdn.microsoft.com/library/en-us/vsdebug/html/vxtskDebuggingClient-SideScript.asp

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

258929 HOWTO: Debug ASP applications manually against Windows 2000 Web Server

Modification Type:MinorLast Reviewed:8/15/2005
Keywords:kbWebBrowser kbScript kbDLL kbweb kbInetDev kbDebug kbbrowsing kbprb KB837316 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.