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.
I have a simple C++ DLL that implements a few custom actions for a WiX installer.
Debugging the custom actions is usually simple: put up a temporary dialog box at the beginning of the action, and attach to the process when the dialog box appears.
But today, whenever I attach to the process, I get the ‘Microsoft Visual Studio is Busy’ bubble appearing at the bottom of the screen. I cannot figure out where this is coming from. Any ideas?
After hours of trying to figure this out, I realized that the problem was that I had debugging symbols enabled in Tools->Options->Debugging->Symbols. The latency in looking up symbols was leading to the apparent lockup.
Clearing the ‘Search the above locations only when symbols are loaded manually’ seems to have alleviated the problem.