Question

If you need a "standalone" CLR debugger (such as .NET 2 offered), SharpDevelop is a good alternative to VS (if you're into that kind of thing).

However, when trying to debug a running ASP.NET application, I did not see w3wp listed in "Attach to Process". Why not?

In the spirit of "Q&A-style" sharing, I'm posting this item I've already figured out. I found that there were two somewhat non-obvious requirements.

Was it helpful?

Solution

SharpDevelop is 32 bit debugging only, so if you are on 64 bit Windows, w3wp might be 64 bit and SD cannot debug it. Simply set IIS application pool to 32 bit and you only get 32 bit w3wp.

Meanwhile, you should try to run SharpDevelop as admin and try again, as admin rights are also necessary.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top