R# 2.0 feedback

Based on 2 days use of R#2, here is some early feedback for you:

What I Like:
- CtrlQ, Ctrl8, CtrlAltShift+N
- R# NUnit support - I like that a lot

What I Want:
- R# run/debug nunit on the context menu
- R# run/debug nunit on a shortcut key combo

Observations:
- R# debugging a unit test is slow (I.E. the actual debugging experience is slow)
- R# NUnit tree does not support standard keyboard navigation.
E.G.
- Backspace on a node should go to the parent
- Left Arrow on a node should collapse the current node or, if collapsed, go to the parent
- etc.

Bugs:
- dot as a completion character on a completion list does not display subsequent intellisense list. See http://www.extraview.co.uk/resharper/NoIntellisenseAfterDot.html
- I have never been able to post exception reports through my client's proxy (reported this seperately). Today I must have had about six R# exception reports - none of which I can easily send you. I am dumping them out to text files. Do you want them?

3 comments
Comment actions Permalink

Hello James,

thank you a lot for your feedback.

In fact, it is possible to run/debug unit tests from variety of different
places - you can do this
from the Unit Test Runner tool window, from the context menu in the Solution
Explorer,
from the context menu in the code editor, and
by clicking the icon on the gutter to the left of the editor (may be I've
failed to remember some
other way). Doesn't it work for you?

Concerning performance of unit test debugging: it seems to depend on the
version of VS you're using,
VS 2003 or VS 2005. In VS 2003, there was no API to attach debugger in the
managed mode only, and
attaching debugger in mixed mode is slow. This was changed in VS 2005, where
unit tests debugging
should work faster.

We've recently fixed a bug with proxy authorization in the exception submitter,
so hopefully the latter will
work for your since the next build.

As for the problem with completion, could you please submit to our tracker?
Thanks in advance.


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

Based on 2 days use of R#2, here is some early feedback for you:

What I Like:
- CtrlQ, Ctrl8, CtrlAltShift+N
- R# NUnit support - I like that a lot
What I Want:
- R# run/debug nunit on the context menu
- R# run/debug nunit on a shortcut key combo
Observations:
- R# debugging a unit test is slow (I.E. the actual debugging
experience is slow)
- R# NUnit tree does not support standard keyboard navigation.
E.G.
- Backspace on a node should go to the parent
- Left Arrow on a node should collapse the current node or, if
collapsed, go to the parent
- etc.
Bugs:

- dot as a completion character on a completion list does not display
subsequent intellisense list. See
http://www.extraview.co.uk/resharper/NoIntellisenseAfterDot.html

- I have never been able to post exception reports through my client's
proxy (reported this seperately). Today I must have had about six R#
exception reports - none of which I can easily send you. I am dumping
them out to text files. Do you want them?



0
Comment actions Permalink

*run/debug unit tests *
from the Unit Test Runner tool window
YES

from the context menu in the Solution Explorer
NO

from the context menu in the code editor
NO

+clicking the icon on the gutter to the left of the editor +
YES

0
Comment actions Permalink

Hello James,

this is really strange, but I've checked, and the menu commands for
running & debugging tests are indeed missed in the places you pointed
out. We've added them.


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

*run/debug unit tests *
from the Unit Test Runner tool window
YES
from the context menu in the Solution Explorer NO

from the context menu in the code editor
NO
+clicking the icon on the gutter to the left of the editor + YES



0

Please sign in to leave a comment.