Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
My project loads significantly faster when I attach it to my w3wp.exe IIS worker process, than when I “Start Debugging”.
However, the same worker process seems to be processing the same amount of modules/DLLs (w3wp.exe) whether I “Start Debugging” or “Attach to Process”.
Why is attaching to a process so much quicker?
“Start Debugging” launches a new instance of the executable with the debugger attached right from the beginning, so the overhead of all the needed debugger calls is incurred from launch, whereas “Attach to Process” attaches to a already running process, so until then your process was running without any additional overhead caused by debugging.