0

for some time i've got a problem debugging my asp.net 3.5 Application with Visual Studio 2012. Each Time i want to observe which values are in an Collection,List or similar classes, Visual Studio hangs for some seconds and then for each Property of the Collection (like Count) there is no Value, but a message which says an timeout occured and i have to step further in the debugger, to activate it again. But when i step further (F10), Visual Studio hangs and i just can kill the w3wp.exe process and start debugging from beginning.

This Problem occurs only in my classic asp.net 3.5 application. Other Asp.net MVC or WinForms applications work just fine!

Anyone an idea?

Chris
  • 21
  • 3

1 Answers1

0

I was also facing this issue and stumbled across this post:

Unable to start debugging on the web server. Could not start ASP.NET debugging VS 2010, II7, Win 7 x64

Dont know how but correcting the username/password of the app pool which was used by the ASP.NET application fixed the issue.

P.S: Application was working fine it not debugged with old app pool credentials.

Hope this helps!

Community
  • 1
  • 1
Gunjit
  • 98
  • 1
  • 5