BUG: The Vs7jit.exe process still runs on the remote server when you end the debugging process (822318)
The information in this article applies to:
- 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
- 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 ASP.NET (included with the .NET Framework) 1.0
- Microsoft ASP.NET (included with the .NET Framework 1.1)
SYMPTOMSWhen you create a Web application on a remote server and
then you start to debug the Web application from the client computer, the
Vs7jit.exe process starts in the server computer. When you manually quit the
Devenv.exe process, you may notice that the Vs7jit.exe process still runs on
the server computer. You may notice this in
Windows Task Manager on the server computer.WORKAROUNDTo work around this bug, manually quit the Vs7jit.exe
process on the server computer. To do this, follow these steps:
- Right-click the taskbar, and then click Task
Manager.
- On the Processes tab, click
vs7jit.exe, and then click End
Process.
- Close Windows Task Manager.
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are
listed at the beginning of this article.
REFERENCES For additional information, click the following article
numbers to view the articles in the Microsoft Knowledge Base: 822316
HOW TO: Create a New ASP.NET Web
Application on a Remote Web Server
318041 HOW TO: Set Up and Use Remote Debugging in Microsoft Visual Studio .NET
Modification Type: | Major | Last Reviewed: | 7/28/2005 |
---|
Keywords: | kbvs2002sp1sweep kbpending kbDeployment kbJIT kbDebug kbWebServer kbWebBrowser kbRemoting kbbug KB822318 kbAudDeveloper |
---|
|