CODEWITHSUNDEEP
asp.netvisual-studio-2008debuggingiis-7
DotNetUser
DotNetUser

Reputation: 6612

Vistual Studio 2008 SP1 debugging not working with IIS process (sometimes)

I am using VS 2008 SP1 on Windows 7 and tyring to debug a ASP.net website project by attaching debugger to w3wp process, I noticed that debugger wont stop at the breakpoint at everytime. I researched a lot on this issue and found that its a known issue see this link: http://support.microsoft.com/kb/957912. I tried hotfix but still I am facing the same issue, its really annoying to test. Anyone had this issue?

Note: I am using Asp.net routing feature which introduced in .net 3.5 SP1.

Upvotes: 2

Views: 539

Answers (2)

slfan
slfan

Reputation: 9129

You have to run Visual Studio as an administrator otherwise you are not allowed to attach the debugger to another process.

Or do you sometimes compile in release mode? You also have to set the option debug='true' in the configuration file (it depends on where you set the breakpoint) and set the correct mode when attaching the debugger (attach to managed code).

The breakpoint is also not hit, when you not run the latest version of the code. Make sure you rebuild the code before you attach to w3wp.exe. Start the code with F5 in debug mode should always work.

Upvotes: 0

Dima
Dima

Reputation: 6741

Check that you select "Managed code" in "attach to" dialog. And, just in case, maybe it's a problem with your routing and there is nothing to do with debugger?

Upvotes: 1

Related Questions