Love the idea of Debugger Canvas - it's especially useful in certain situations. And I had found performance to be pretty decent. However, in a large ASP.NET MVC 3 project I'm working on, debugging was abysmally slow - Visual Studio would go
to "Not Responding" as soon as the code was to hit a breakpoint - and only come back after about 2 minutes. And this was even when Debugger Canvas option was turned off through the toolbar button.
I uninstalled Debugger Canvas, and everything was back to normal.
Hi Andrew, sorry to hear the performance is so bad on your project. Thanks for giving it a shot, and for giving us feedback!
How large is your ASP.NET MVC 3 project? And how many other projects are in the solution?
Also you may have noticed in the Extension Manager that Debugger Canvas installs two components, 1) itself, and 2) a package called VS Fragments. When you uninstalled Debugger Canvas, did you also uninstall VS Fragments at the same time? It would
help us narrow down the issue if you could tell us whether performance is still bad when VS Fragments is installed but Debugger Canvas is not. That way we could tell which package is causing the slowdown.
Kael Rowan | Research Software Design Engineer | Human Interactions in Programming | Microsoft Research