BUG: The Vs7jit.exe process still runs on the remote server when you end the debugging process

When 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.

To work around this bug, manually quit the Vs7jit.exe process on the server computer. To do this, follow these steps:

1. Right-click the taskbar, and then click Task Manager.
2. On the Processes tab, click vs7jit.exe, and then click End Process.
3. Close Windows Task Manager.

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

Steps to Reproduce the Behavior

1. Start Microsoft Visual Studio .NET.
2. Create a Web application in Visual Basic .NET or Visual C# .NET on the remote server.
   
   For additional information about how to create a new ASP.NET Web Application on a remote Web server, click the following article number to view the article in the Microsoft Knowledge Base:
   822316� HOW TO: Create a New ASP.NET Web Application on a Remote Web Server
3. Double-click the designer to open the Code Editor. By default, the Page_Load event is displayed.
4. Add the following code to the Page_Load event:
   
   Visual C# .NET Code

   Response.Write("Hello!");

   Visual Basic .NET Code

   Response.Write("Hello!")

   On this line, press F9 to set a breakpoint.
5. On the Debug menu, click Start. The Vs7jit.exe process starts on the server computer.
6. On the client computer, right-click the taskbar, and then click Task Manager.
7. On the Processes tab, click devenv.exe, and then click End Process.
8. On the server computer, right-click the taskbar, and then click Task Manager.
9. On the Processes tab, you may notice that the Vs7jit.exe process is still running.

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