Why am I unable to Debug my ASP.NET website in Visual Studio?

Question

I used to be able to attach to my w3wp process and Debug my web application, but this is not working anymore. I have no idea what changed to break this. I\'m using Visual St

Answer 1

Check your web.config for

<compilation debug="true">...

Answer 2

I faced the same issue. The w3wp process took a lot of memory and did not want to be reset on web application publishing.

Press Ctrl+Alt+Delete > Go to "Processes" tab > find w3wp process and kill it. Run the app again (if this is an mvc app, just go to a related url to automatically recreate w3wp process).

Warnings will disappear after that.

Answer 3

On OpenVMS we just used to:

Compile/Debug then Link/Debug

and that was it! Simples!!

but seriously, make sure the file you have your Debugger.Break line in, has 'Copy always' set in its Properties before re-building

Answer 4

I know this issue has been open for some time, but I think it is the same as I experienced:

I could not debug my .aspx server side code. I had a working WepApp AnyCPU project and I wanted to link to some x86 dlls, so I created an x86 debug target. Did similar things, rebuilt, stopped the development web server, rebooted, clear temporary files, all to no avail.

Fixed the problem by changing the target folder to bin\ (was bin\x86\Debug).

Answer 5

in the "Attach to process" dialog, click the checkbox (near the bottom) for "show processes from all users" and if you see two w3wp.exe processes, try the other one.

One should have a comments/description value of something like T-SQL, managed somethingoranother. This is the one you want.

Answer 6

I had this problem recently and I ended up first making sure Visual Studio was not running at all on the system.

Then went into this folder and deleted all its content:

C:\windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\