Debug Unit test break keyboard. Build 220

This morning I've uninstalled the 219 build and installed the 220.
After that I've relaunched my solution and I've tried to debug a unit test, in another file I have a couple of error so the compilation failed.
From that moment the keyboad in VS doesn't work anymore, all I can do is to close and restart the IDE.
I've tried to compile the solution with the CtrlShiftB, it finds errors but the keyboard continue to work.

With this release I've noticed a huge performance downgrade... it's more, more, more slower than the 219 build.

Thank you,
Antonio.

6 comments
Comment actions Permalink

With this release I've noticed a huge performance downgrade... it's more,
more, more slower than the 219 build.


VS2003 or VS2005?

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

ops... I've forgotten to mention...
VS2003

0
Comment actions Permalink

Hello Antonio,

do you mean that VS hangs after you try to debug unit tests with ReSharper?
Thanks.


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

This morning I've uninstalled the 219 build and installed the 220.

After that I've relaunched my solution and I've tried to debug a unit
test, in another file I have a couple of error so the compilation
failed.

From that moment the keyboad in VS doesn't work anymore, all I can do
is to close and restart the IDE.

I've tried to compile the solution with the CtrlShiftB, it finds
errors but the keyboard continue to work.

With this release I've noticed a huge performance downgrade... it's
more, more, more slower than the 219 build.

Thank you,
Antonio.



0
Comment actions Permalink

No, VS doesn't hang, only the keyboard stop working, I mean that if I type everything, the ide don't show anything, but if I use the mouse I can access everything (menu, select text, RS functions etc.).
The keyboard continue to work correctly outside the ide, (ex. if I open a notepad I can write inside it etc.)

0
Comment actions Permalink

Ah this happens only if there are errors in the build time, if the build go well the debug work.
I have another issue with the debug unit test but shortly I'll open a new thread.
Antonio

0
Comment actions Permalink

The problem seems solved in build 221.
Thank you.

0

Please sign in to leave a comment.