Unblocking "good" VS features
Hi, there are a number of visual studio features that Resharper is blocking,
even though they are extremely useful to development. Can someone comment on
the reasons behind them and when they will be available again?
object in VS05 & VS08 originally dynamically generates a text file view of
the selected object with documentation if the original source code is not
available.
After R# installation, only old object browser is available. Text view is
far superior, as it allows text searching and manipulation using large
number of text processing tools. R# 2.5 still had this available (only F12
shortcut was overridden by default), whereas after v3 it disappear
completely.
http://www.jetbrains.net/jira/browse/RSRP-35547
Ctrl+Enter keystroke in most editors including VS inserts a new line
before the current one and moves the cursor there. Disabled in R#. Was
available earlier (v3?), but was disabled afterwards.
http://www.jetbrains.net/jira/browse/RSRP-45672
Thanks!!!
Please sign in to leave a comment.
You can just remap those features to different keys, or remap the Reshaprer
features (or use the VisualStudio key mapping), can't you?
"Yuri" <zapodlo@gmail.com> wrote in message
news:fofekk$cp0$1@is.intellij.net...
>
>
>
>
>
>
>
>
>
>
>
>
>
I wish it was possible to enable it via key mapping, but the
Edit.GotoDeclaration action no longer works, and a new action
Resharper.Resharper_GotoDeclaration uses object browser, not metadata source
code. Can anyone from the R# team comment please?
Thanks!
"Paul Bradshaw" <pbradshaw@advsol.com> wrote in message
news:fohuuu$n4f$1@is.intellij.net...
>
>> Hi, there are a number of visual studio features that Resharper is
>> blocking, even though they are extremely useful to development. Can
>> someone comment on the reasons behind them and when they will be
>> available again?
>>
>>
>>
>> * Source code view of objects ( screen). Pressing F12 on
>> an object in VS05 & VS08 originally dynamically generates a text file
>> view of the selected object with documentation if the original source
>> code is not available.
>>
>> After R# installation, only old object browser is available. Text view is
>> far superior, as it allows text searching and manipulation using large
>> number of text processing tools. R# 2.5 still had this available (only
>> F12 shortcut was overridden by default), whereas after v3 it disappear
>> completely.
>>
>> http://www.jetbrains.net/jira/browse/RSRP-35547
>>
>>
>>
>> * Ctrl+Enter keystroke in most editors including VS inserts a new line
>> before the current one and moves the cursor there. Disabled in R#. Was
>> available earlier (v3?), but was disabled afterwards.
>>
>> http://www.jetbrains.net/jira/browse/RSRP-45672
>>
>>
>>
>> Thanks!!!
>>
>>
Hello Yuri,
the corresponding JIRA issue (link in the original post) is currently not
planned for 4.0. However, we may reconsider this decision if so many users
like decompiled source more than Object Browser.
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
>> You can just remap those features to different keys, or remap the
>> Reshaprer features (or use the VisualStudio key mapping), can't you?
>>
>> "Yuri" <zapodlo@gmail.com> wrote in message
>> news:fofekk$cp0$1@is.intellij.net...
>>
>>> Hi, there are a number of visual studio features that Resharper is
>>> blocking, even though they are extremely useful to development. Can
>>> someone comment on the reasons behind them and when they will be
>>> available again?
>>>
>>> * Source code view of objects ( screen). Pressing F12
>>> on an object in VS05 & VS08 originally dynamically generates a text
>>> file view of the selected object with documentation if the original
>>> source code is not available.
>>>
>>> After R# installation, only old object browser is available. Text
>>> view is far superior, as it allows text searching and manipulation
>>> using large number of text processing tools. R# 2.5 still had this
>>> available (only F12 shortcut was overridden by default), whereas
>>> after v3 it disappear completely.
>>>
>>> http://www.jetbrains.net/jira/browse/RSRP-35547
>>>
>>> * Ctrl+Enter keystroke in most editors including VS inserts a new
>>> line before the current one and moves the cursor there. Disabled in
>>> R#. Was available earlier (v3?), but was disabled afterwards.
>>>
>>> http://www.jetbrains.net/jira/browse/RSRP-45672
>>>
>>> Thanks!!!
>>>
Dmitry Shaporenkov wrote:
Do not replace object browser with metadata browse. I like object
browser. If you decide to add metadata, then ok, but not to remove
object browser. Can be an settings which browser (object/metadata) want
to open when "Goto declaration" is executed.
--
Peter Sulek
terrorix@centrum.sk
XanaNews ver. 1.18.1.6
Hello Peter,
surely, if we support metadata navigation, there will be an option allowing
to choose between Object Browser and metadata. Nobody is going to drop
Object Browser support.
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
>> Hello Yuri,
>>
>> the corresponding JIRA issue (link in the original post) is currently
>> not planned for 4.0. However, we may reconsider this decision if so
>> many users like decompiled source more than Object Browser.
>>
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> I wish it was possible to enable it via key mapping, but the
>>> Edit.GotoDeclaration action no longer works, and a new action
>>> Resharper.Resharper_GotoDeclaration uses object browser, not
>>> metadata source code. Can anyone from the R# team comment please?
>>>
>>> Thanks!
>>>
>>> "Paul Bradshaw" <pbradshaw@advsol.com> wrote in message
>>> news:fohuuu$n4f$1@is.intellij.net...
>>>
>>>> You can just remap those features to different keys, or remap the
>>>> Reshaprer features (or use the VisualStudio key mapping), can't
>>>> you?
>>>>
>>>> "Yuri" <zapodlo@gmail.com> wrote in message
>>>> news:fofekk$cp0$1@is.intellij.net...
>>>>> Hi, there are a number of visual studio features that Resharper is
>>>>> blocking, even though they are extremely useful to development.
>>>>> Can someone comment on the reasons behind them and when they will
>>>>> be available again?
>>>>>
>>>>> * Source code view of objects ( screen). Pressing
>>>>> F12 on an object in VS05 & VS08 originally dynamically generates a
>>>>> text file view of the selected object with documentation if the
>>>>> original source code is not available.
>>>>>
>>>>> After R# installation, only old object browser is available. Text
>>>>> view is far superior, as it allows text searching and manipulation
>>>>> using large number of text processing tools. R# 2.5 still had this
>>>>> available (only F12 shortcut was overridden by default), whereas
>>>>> after v3 it disappear completely.
>>>>>
>>>>> http://www.jetbrains.net/jira/browse/RSRP-35547
>>>>>
>>>>> * Ctrl+Enter keystroke in most editors including VS inserts a new
>>>>> line before the current one and moves the cursor there. Disabled
>>>>> in R#. Was available earlier (v3?), but was disabled afterwards.
>>>>>
>>>>> http://www.jetbrains.net/jira/browse/RSRP-45672
>>>>>
>>>>> Thanks!!!
>>>>>
Hello,
The object browser better suits for reference and navigation than unformatted
plain text, so R# is currently navigating to that view. Should we go to plaintext,
no R# features would be available there, like File Structure and Goto File
Member, as R# does not support loose C# files. This renders the plaintext
view mostly useless. As for text processing, R#'s features from the Generate
menu, like Implement and Override, reduce the need in that sort of things.
This explains the current selection, I think.
There are some advanced DLL reflection features planned, regarding navigation
also, but not for the 4.0 version.
—
Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”
I do not think having plaintext file code without R# features is useless. If
you view all R# issues in Jira (including closed), and sort them by votes,
RSRP-35547 is the fourth most voted one - out of over 50,000! I guess there
is a good number of developers out there who were bothered enough to find
it, register in Jira, and vote for it. One blogger even went out as far as
posting a large entry describing reasoning at
http://blog.excastle.com/2007/02/11/resharper-day-11-code-navigation/.
I was by no means proposing to disable object browser - it has its good
uses. Rather, it is the fact that good existing functionality was disabled
without any ways of getting to it once R# is installed.
R# is a wonderful assistant tool, but R# features are not as needed when
browsing the generated plaintext file. Its primary function is quick text
search within class declaration and documentation, and other (often regex)
text based operations, which tends to be much more convenient (IMHO).
Regardless, I do not think R# should simply disable existing functionality
just because it does not appear to be useful to some developers - there
should always be end user choice what to have.
Still, I think R# is the best add-on a .NET developer can possibly wish for,
and I am eagerly awaiting v4! Thank you for a wonderful product.
"Serge Baltic" <baltic@intellij.net> wrote in message
news:dc0986bfb4de98ca3c5e120aa06f@news.intellij.net...
>
>> * Source code view of objects ( screen). Pressing F12
>> on an object in VS05 & VS08 originally dynamically generates a text
>> file view of the selected object with documentation if the original
>> source code is not available.
>
>
>
>
The problem with VS2k8's object browser, which I reported earlier
(http://jetbrains.net/jira/browse/RSRP-54012) makes it pretty much unusable
with types outside of loaded solution.
"Serge Baltic" <baltic@intellij.net> wrote in message
news:dc0986bfb4de98ca3c5e120aa06f@news.intellij.net...
>
>> * Source code view of objects ( screen). Pressing F12
>> on an object in VS05 & VS08 originally dynamically generates a text
>> file view of the selected object with documentation if the original
>> source code is not available.
>
>
>
>
Hello,
Well, ... The thing is, the same issues would apply to the "goto text" feature.
Showing plaintext instead of the tree does not seem to make it easier to
tell VS which exactly thing to show, as navigation is performed essentialy
by passing freehand text presentations of the entities.
—
Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”
Hello,
Not totally useless, of course, but that would be a major inconsistency in
R# behavior to ignore some of the source code files it opens, where none
of the actions are available, no coloring, etc. That's a thing to bother.
>If you view all R# issues in Jira (including closed), and
Frankly speaking, voting is not the main driving force on the JIRA issues.
That's mainly because they're inrepresentative, that is, only some issues
are voted for, and relatively few people do vote.
...until you try some Goto Usage on a library method you've found, just to
see if it's used, and how. Makes some sense, right?..
Users want to have everyting, of course. But some things are harder to implement
than others. The investigation on how to make VS open the text view is not
yet complete. We do not have any compulsion to hide features for nothing,
and in this case the Object Browser was more eager to host the navigation.
—
Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”
Hello all,
Simply put, Resharper 3 breaks GotoDeclaration (save for framework types). (in v2k8 and/or vs2k5?)
It simply shows the object browser but fails to navigate to the correct type in the correct assembly, as has been noted in the bugreports.
From that, I find it surprising that people are even discussing whether the object browser is good or not. If it doesn't work, it isn't doing me any good.
But IMNHO, the object browser is a stupid toy forcing yet another representation decoding task upon us.
Since I read code most of the day, I'm pretty much sure I do it faster than any treeviewer that the 90's just called and wants back (along with it's buddy the 80's who wants all the CASE tools we have in our closets).
Viewers, pffft. :)
http://jetbrains.net/jira/browse/RSRP-54012
http://jetbrains.net/jira/browse/RSRP-35547
(FWIW, this is not a new feature. Effectively removing a feature introduced by vs2k5 is a defect (not a bug nor a fault, but a defect just the same). Like any good dev, we can try featureing any defect but we are all devs here: It was a good feature in vs 2k5 and still is.
Allowing us to use that view and R# together is not a R# feature - it is a defect fixed)
Lots of love!
(using R# 3 with vs 2k8 and sometimes 2k5)
PS
If voting is deemed uninteresting, I think you should remove it. It's a datapoint; use it or remove it. People put time into voting, it would be more respectful to them to remove the option if it is deemed uninteresting.
PS2
Sorry for the ranting tone, I really love resharper! It's VS++++! Keep churning!