16 comments
Comment actions Permalink

This week I am trying Rider for the first time and it's awesome, but this feature + analogue of CodeLense from VS would make it ultimately perfect.

0
Comment actions Permalink

Is this feature available now? We would like to give a try for Rider but we use Peek-Definition(Alt-F12) a lot and can't code with it :)

0
Comment actions Permalink

Hi all,

Thanks for your feedback! There's an action called Quick Definition (Ctrl+Shift+I) that Rider inherits from the IntelliJ platform, which is similar to Visual Studio's Peek Definition. Unfortunately, it has a bug currently, which you may want to follow: RIDER-3178.

It is worth noting that IntelliJ's Quick Definition doesn't allow to actually modify code right inside the displayed definition. How often do you use this feature? Would a read-only view meet your needs?

Antivortex Please vote for CodeLens feature here: https://youtrack.jetbrains.com/issue/RIDER-2278

 

0
Comment actions Permalink

Ctrl+Shift+I does nothing when I select any class or method which I would like to quick view in Raider.

If I search for Quick Definition in settings it shows that option is mapped to Ctrl+Shift+I, also I find the same shortcut map in Code -> Implement Methods. 

Answering to your question about edit mode for Quick Definition, actually I don't need it, in VS I use Peek-Definition only for quick code review while coding.

0
Comment actions Permalink

@Julian 

Thanks for your response.

Visual studio Quick Definitions was one of the most effective features of the IDE. It improve my, my many of my colleges productivity immensely. 

Having this feature in rider is a must for complicated code base ( enterprise projects), to navigate and edit easily.

0
Comment actions Permalink

I also would very highly appreciate that feature as this was a real kickassPullFactor for VS for me.  Also something like codelens, displaying the amount of references next to a member is genious. Why is this not in such a  powerful IDE like Rider yet ?

1
Comment actions Permalink

This is one of the main features that are missing in Rider. Can we get any info if this will be implemented in near future?

1
Comment actions Permalink

This is basically the only reason I dont rider, it looks like RIDER-3178 has been updated recently

 

Ctrl + Shift + I does not do anything when I press it, can we please get an update on when this will be fixed? 

1
Comment actions Permalink

Just a comment, I use Rider because I also use IDEA for Java projects and it's nice to have the overlap of shortcuts (I realize you can load the shortcuts into VS with ReSharper, but I have a lot of customization that has to do with Vim key bindings and it was much easier to map everything over from IDEA). I also just love JetBrains products and outside of this feature I haven't had any other issues with Rider (granted I've only been using it for about a month now). But I use this A LOT in IDEA and definitely hope it is supported in the near future.

That being said, if you are in a similar situation where you want to avoid using VS, you can use Ctrl + Shift + G to navigate to the actual file and line of the declaration (or other options like implementations, etc). This is obviously not a great solution because you will be opening tabs up like a madman and constantly be flipping between them, but it's what I currently do because overall it's not worth it to switch to VS over this one feature (I'm also very efficient at tab management because I used Vim inside a terminal for a while).

To be clear, VS might be the better IDE for C# (and other Windows languages), but I do not code exclusively in C#. Therefore I like JetBrains because as a whole they have IDE support for whatever I need and it is extremely convenient to have almost the exact same UI throughout these different IDE's (for example, setting up build configs is the same, Git support is the same, etc).

0
Comment actions Permalink

Ajohnston1219, thanks a lot for your feedback! We work on it. Stay tuned :) 

0
Comment actions Permalink

Any update on this? Is this functionality already in the road map?

0
Comment actions Permalink

Hi Andre!

We've improved Quick Definition (RIDER-3178) in 2019.3, please, try it. 

0
Comment actions Permalink

Hi,

 

I'm running 2019.3.3 and while the current Quick Definition is close to what I'd hope for, ideally it would embed the peeked definition inside the active editor (Similar to VS). Instead, it currently opens up a mini-window adjacent to the queried code which raises several issues:

  1. mini-window can block other code I'm trying to read or juxtapose with the peeked definition.
  2. Clicking back to editor to write new code, involving the peeked definition, puts the mini-window in the background. Can't reference the definition I queried without the undesirable additional effort of returning the mini-window to the foreground.

Is there any initiative towards addressing these issues, perhaps by embedding the peeked definition in the editor?

1
Comment actions Permalink

Im in the same boat as David, I would much rather it behave more like how Visual Studio handles it. I agree its more effort to work with this implementation. In addition to what David said about blocking code, usually when I want a quick definition, I am wanting to view two pieces of code from separate files at the same time and potentially write to both of them. The way it behaves now is that if I want to edit the original file, then the window disappears. 

1
Comment actions Permalink

Hi David, Cory, 

thank you for the feedback! I've created an issue RIDER-42810 for your suggestion, please, feel free to follow it and vote. 

0
Comment actions Permalink

If you're like me and use the Visual Studio key layout in Rider and are having trouble getting this feature to work by pressing Alt+F12, check if you have any other software running in the background that might be intercepting the key codes.

In my case, the Geforce Experience in-game overlay had a bunch of Alt+Function keys bound to various actions by default and was preventing the key codes from reaching Rider. Disabling the in-game overlay immediately fixed the problem.

Hopefully this saves someone more time than I spent figuring this out.

0

Please sign in to leave a comment.