Unit Testing Fails after Hibernate

Oh and I thought I'd add another small bug. If you change the Unit Test
Runner in VS 2003 to auto hide on the bottom of the IDE, for example, it
will lose track of it's height and will need to be "re-expanded" each
time a test is run. For example, set it to auto hide while docked to the
bottom, run a test or two, and then put your mouse over the "Unit Test
Runner" tab on the bottom once it's hidden and you'll just see a sliver
of the top border appear (probably 2-4 pixels) which you can
subsequently grab and drag up to show it again.

Greg Fodor wrote:

I've noticed that the "Exploring Assembly" dialog locks up when trying
to run the unit test runner after I bring my laptop out of Hibernate.
This happens every time, and requires that I restart VS.NET.

Hello Greg,

concerning this issue, it is not recommended to set 'Auto Hide' for ReSharper
tool windows.
It is a known problem that 'Auto Hide' ReSharper windows may behave oddly
in VS 2003, you
can even hide them without an obvious method to bring back. It's not clear
by now if it is a ReSharper
issue or a VS 2003 internal problem.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Oh and I thought I'd add another small bug. If you change the Unit
Test Runner in VS 2003 to auto hide on the bottom of the IDE, for
example, it will lose track of it's height and will need to be
"re-expanded" each time a test is run. For example, set it to auto
hide while docked to the bottom, run a test or two, and then put your
mouse over the "Unit Test Runner" tab on the bottom once it's hidden
and you'll just see a sliver of the top border appear (probably 2-4
pixels) which you can subsequently grab and drag up to show it again.

Greg Fodor wrote:

>> I've noticed that the "Exploring Assembly" dialog locks up when
>> trying to run the unit test runner after I bring my laptop out of
>> Hibernate. This happens every time, and requires that I restart
>> VS.NET.
>>