Visual Studio Debugging is not attaching to WebDev.WebServer.EXE
Posted
by Aaron Daniels
on Stack Overflow
See other posts from Stack Overflow
or by Aaron Daniels
Published on 2009-10-14T15:26:13Z
Indexed on
2010/03/26
17:33 UTC
Read the original article
Hit count: 538
I have a solution with many projects. On Debug, I have three web projects that I want to start up on their own Cassini ASP.NET Web Development servers. In the Solution Properties - Common Properties - Startup Project, I have Multiple startup projects chosen with the three web applications' Action set to Start. All three web development servers start, and all three web pages load.
However, Visual Studio is only attaching to two of the WebDev.WebServer.EXE
processes. I have to manually go attach to the third process in order to debug it with the debugger.
This behavior just started happening, and I'm at a loss as to how to troubleshoot this. Any help is appreciated.
EDIT:
Also to note, I have stopped and restarted the development servers several times with no change in behavior. Also, when attaching to the process manually, I see that the Type property of the two automatically attached WebDev.WebServer.EXE
processes is Managed, while the Type property of the unattached WebDev.WebServer.EXE
process is TSQL, Managed, x86. When looking at the project's properties, however, I am targeting AnyCPU, and do NOT have SQL Server debugging enabled.
EDIT:
Also to note, the two projects that attach correctly are C# web applications.
<ProjectTypeGuids>{349c5851-65df-11da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc}</ProjectTypeGuids>
The project that is not attaching correctly is a VB.NET web application.
<ProjectTypeGuids>{349c5851-65df-11da-9384-00065b846f21};{F184B08F-C81C-45F6-A57F-5ABD9991F28F}</ProjectTypeGuids>
EDIT:
Also to note, the behavior is the same on another workstation. So odds are that it's not a machine specific problem.
© Stack Overflow or respective owner