Your comments

Thanks a lot for your feedback! That's a shame about VS2012. When we implement pinning, we'll also implement a proper keyboard shortcut for it, that automatically takes the entire expression, like our QuickWatch (Shift+F9) shortcut does.
As of BugAid 1.0 Release Candidate (version 0.5.2004.7664), BugAid menu now shows up as soon as you open Visual Studio.
Our new Early Access Build supports VS11 Beta, so you can try it out right now! We plan to publish it as a regular release once we've done a bit more testing, very soon.
Thank you very much for your feedback. That's a good idea - we'll change the text in the Welcome email.
Thank you very much for your feedback! We've heard from a couple of other users who requested the same thing. We are looking into ways in which we could improve the performance of Search and Filter by an order of magnitude, so that you'll be able to complete very deep and far-reaching searches in a reasonable time period.
No problem at all, we're happy to answer any question you have. :)
Hi Daniel,

Actually, editing values from BugAid's on-hover data-tip should work fine. The only difference from the default Visual Studio experience is that you have to double-click on the variable's value to start editing (rather than a single click). We made it a double-click instead of a single click because we were often annoyed when we accidentally caused Visual Studio to start editing even when it's not what we intended.

Thanks you for your request. I can definitely see the need for a "persisted watch list" as you describe, that persists expressions as text between debug sessions and even after you close Visual Studio. The main deterrent we might have from implementing such a feature is that it would only work well for expressions that access data through a static class (ie, successfuly evaluating them does not depend on debug context), and that might be confusing to the novice user.

As for automatically recreating an Object ID on the persisted expressions automatically, I think there are a couple of problems: (1) Since we can only Make Object ID on the first time the user breaks in the debugger, the moment in which we do it might differ from debug session to debug session, and this could lead to a lot of confusion. (2) It'll be a little inconsistent, because Make Object ID only works on reference types, and would fail on value types.

So in light of this, I think it might be best if we implement this idea but without automatically making object IDs, and seperately implement Julien Lebosquain's idea for a "Tracked References" window. Does that make sense to you?

Hi Ben,

Thank you for your suggestion. We agree that the debugging experience in Visual Studio really breaks down when you use lambda expressions or query expressions, and this is something we are looking at for BugAid 2.0. 

Thank you very much for your feedback. Unfortunately, we cannot directly solve this issue as it stems from an inherent limitation of Visual Studio. If you'd like to help, please upvote our request for Microsoft to fix this on MS Connect.

Barring any co-operation from Microsoft, we intend to try and implement the 2nd solution you suggested (after the release of BugAid 1.0). We do realize that the current situation is not great and we thank you for your understanding.