0

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.

Community
  • 1
  • 1
harpo
  • 41,820
  • 13
  • 96
  • 131
  • 1
    SharpDevelop is 32 bit debugging only, so if you are on 64 bit Windows, w3wp might be 64 bit and SD cannot debug it. Meanwhile, you should try to run SharpDevelop as admin and try again, as admin rights are also necessary. – Lex Li Nov 20 '13 at 17:22
  • @LexLi, post that as an answer and I'll accept it. You hit both points. Specifically, you can make the WP show up by setting "Enable 32-bit Applications" for that app pool in IIS. – harpo Nov 20 '13 at 17:51

1 Answers1

6

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.

Lex Li
  • 60,503
  • 9
  • 116
  • 147
  • +1 for helping me *again* when I found this question myself a year later! – harpo Oct 29 '14 at 01:43
  • This is getting ridiculous. Well, at least I only need the debugger once a year! – harpo Oct 08 '15 at 16:02
  • @harpo Microsoft has stood up and provided VS Community Edition. You can see SharpDevelop has stopped active development. – Lex Li Oct 09 '15 at 00:16