Drat. Well I just found a bug related to using the wrong debugger for a given .Net runtime version.
Jeff. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mark Kharitonov Sent: Saturday, August 15, 2009 2:52 AM To: MbUnit.User Subject: MbUnit Re: "Could not evaluate expression" error message in the watch window when debugging a unit test method. Nope. Up to 3.5. I am using VS2008Pro. On Aug 15, 12:46 pm, "Jeff Brown" <[email protected]> wrote: > Out of curiosity, do you have .Net Framework 4.0 installed and are you > running Visual Studio 2008? > > Jeff. > > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On > > Behalf Of Mark Kharitonov > Sent: Thursday, August 13, 2009 1:54 AM > To: MbUnit.User > Subject: MbUnit Re: "Could not evaluate expression" error message in > the watch window when debugging a unit test method. > > I wish it was so. But it is not. > I am debugging right now and this VS reports "The name 'factoryMethod' > does not exist in the current context". I am debugging a Debug build > without any optimizations. The debugger refuses to show the values. It > happens only when debugging unit tests. Normal application debugging works fine. > Any more ideas? > Thanks. > > On Aug 11, 9:34 pm, "Jeff Brown" <[email protected]> wrote: > > The debugger probably timed out evaluating a previous exception. It > > should resume evaluating expressions after the next single-step. > > > Debugger performance has been the focus of several optimizations in > > the v3.1 series. You might try out a recent nightly build (like > > 3.1.275.0) although I recommend waiting a couple of days until the > official v3.1 release. > > >http://ccnet.gallio.org/Distributables/ > > > Jeff. > > > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] > > On > > > Behalf Of Mark Kharitonov > > Sent: Tuesday, August 11, 2009 9:41 AM > > To: MbUnit.User > > Subject: MbUnit "Could not evaluate expression" error message in the > > watch window when debugging a unit test method. > > > Hi. > > I use Gallio 3.0.6 and TestDriven.NET 2.23.2494. > > I am attaching a snapshot of debugging session in VS2008 Pro. > > Note the m_coll member variable of the test fixture. In the watch > > window VS tells us that it "could not evaluate expression", in the > > locals window, however, expanding this shows the correct value of m_coll. > > > This is pretty annoying, since hovering over a variable in a debug > > session shows the same "could not evaluate expression" message, just > > like in the watch window. > > > The snapshot is here > -http://groups.google.com/group/MbUnitUser/web/GallioDebugSession.JPG. > > > Any ideas? > > > Thanks.- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/MbUnitUser?hl=en -~----------~----~----~----~------~----~------~--~---
