How to troubleshoot and debug Visual Studio design mode errors?

Jake picture Jake · Dec 4, 2012 · Viewed 12.4k times · Source

Using Windows 7 and Visual Studio 2010, I am writing a C# custom UserControl. I was coding in code view for weeks and recently when I tried to switch to design mode, Visual Studio hanged, "NOT RESPONDING". I can wait for an hour, and still nothing happens. Clicking on the close button it gives the "Do you want to wait, close, restart and send information to Microsoft" dialog.

Is there a way to (stack)trace the code that the designer is trying to execute? Maybe design-time trace messages or breakpoints?

Answer

Dr. Andrew Burnett-Thompson picture Dr. Andrew Burnett-Thompson · Mar 24, 2014

For Visual Studio 2010, this answer does the job.

For Visual Studio 2012 or above, what you need to do is actually debug the Visual Studio Designer process. The process you want to debug is called XDesProc.exe

Enter image description here.

I do the following:

  • Open two instances of Visual Studio both pointing to the same solution
  • Close all windows in both.
  • Kill all XDesProc.exe instances in Task Manager
  • In Visual studio instance A, open any view (not one that has the exception). This will start the XDesProc designer process for Visual Studio Instance A
  • In Visual Studio instance B, attach to process on XDesProc.exe and set your breakpoints, or, set Break on exceptions
  • In Visual Studio instance A, open the view (that has the exception)
  • Visual Studio B should break.

Enter image description here

If you missed it, or need to restart the steps, start again from step (2) 'Close all windows' killing XDesProc instances. Sometimes the designer starts up once and caches values, and you will need to have a clean, non-exception designer to track down the problem.