[213] First 2.0 impressions

I've been using R# with vs 2003 since the fist EAP and I love it. I've moved to vs 2005 and finally took the plunge to try R# 2.0 with it. Unfortunately, 2.0 is a huge memory hog, much more so than 1.5 was on vs 2003. Is this just the cost of all the new features or will this be addressed before the release?

Before I uninstalled it, a few things jumped out at me:
- R# quick tips (or whatever they are called) are not integrated with VS ones, nor do they look anything like the VS smart tags. I recall reading earlier on that you were looking at better integration, what happened? If they must be separated, can they be styled to match the look of the VS smart tags?
- R# takes over the F6 command, which is "Build" in VS'05 and something I've been conditioned to. I am sure this will be an issue with many people picking up R# after vs'05.
- R# did not always offer a way to fix a warning condition even when the cursor was placed at the offending like using the Go to Next command.

Upon uninstall, R# remained in the splash screen and the menu bar. I reset the settings to get rid of the menu bar presence, but the R# icon+text are still in the splash screen.

-Michael

3 comments
Comment actions Permalink

Hello michael,

thanks for your feedback!

We're working on reducing memory footprint right now. Actually we expect
significant improvements in the
nearest EAP builds. In any case, memory consumption of 2.0 will not be any
higher than it was in 1.5.

Concerning 'R# quick tips', I'm not sure if you really mean quick fixes or
context actions which are very similar in
appearance. They are indeed not integrated with VS smart tags. First, not
so many users have requested this
integration. Second, VS smart tags and ReSharper quick fixes are invoked
from user interface in different ways, so
it's not clear how seamless such an integration would be. Third, implementing
this integration requires some work, and we've decided
to sacrifice it in favor of other features. However, we may reconsider our
decision if there are many complaints about it.

F6 command - you can always reassign a command manually if you don't like
its shortcut. Most of key combinations
are already in use by VS, and it's difficult to find one that being re-assigned
would satisfy everyone.

As for not showing quick fixes for a warning, this is a known problem - they
may appear at a wrong position, if
there are collapsed regions in the file, so it's easy to overlook them.

That R# remains in the splash screen after uinstallation is odd. Did the
uninstallation complete normally? R#'s remains
in VS menu is another known problem, it will be addressed before the final
release. This doesn't happen with VS 2003,
so we suspect it has something to do with VS itself, although I well understand
that this makes no difference for an
end user.

Thanks again.


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

I've been using R# with vs 2003 since the fist EAP and I love it. I've
moved to vs 2005 and finally took the plunge to try R# 2.0 with it.
Unfortunately, 2.0 is a huge memory hog, much more so than 1.5 was on
vs 2003. Is this just the cost of all the new features or will this be
addressed before the release?

Before I uninstalled it, a few things jumped out at me:

- R# quick tips (or whatever they are called) are not integrated with
VS ones, nor do they look anything like the VS smart tags. I recall
reading earlier on that you were looking at better integration, what
happened? If they must be separated, can they be styled to match the
look of the VS smart tags?

- R# takes over the F6 command, which is "Build" in VS'05 and
something I've been conditioned to. I am sure this will be an issue
with many people picking up R# after vs'05.

- R# did not always offer a way to fix a warning condition even when
the cursor was placed at the offending like using the Go to Next
command.

Upon uninstall, R# remained in the splash screen and the menu bar. I
reset the settings to get rid of the menu bar presence, but the R#
icon+text are still in the splash screen.

-Michael



0
Comment actions Permalink

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d9d22f68c7d61f8afae960@news.intellij.net...

F6 command - you can always reassign a command manually if you don't like
its shortcut. Most of key combinations
are already in use by VS, and it's difficult to find one that being

re-assigned

would satisfy everyone.


Something that would help a lot for this issue of reaffecting the keys would
be an additionnal screen during the installation (or on the first startup),
showing the conflicts and offering to change/skip/force the reassignation.
I have no idea if something like this can be done, but having to constantly
reassign my shortcuts after each new build has been bugging me too.

The easiest way I've found around this is to export the keyboard settings
before uninstalling the previous build, doing the uninstall/reinstall and
then re-importing the settings. It missed some cases (can't remember
exactly, I'll try it again with the next build anyway :), but it was much
better than having to redo everything. But then, it also misses any
changes/additions in the predefined RS shortcut keys.

Regards,

Lionel


0
Comment actions Permalink

I'll keep an eye on announcements and will try again when the memory footprint is gotten under control. FWIW, R# did appear to uninstall w/o any errors (this is in regards to R# remainin in the splash screen).

Thanks!
-Michael

0

Please sign in to leave a comment.