Extract Method does not appear on the editor context menu #597
Comments
|
Moving to 3.0 - this does not meet the bar for 2.2 updates any more. |
|
C# has moved this to Quick Actions |
DinoV
pushed a commit
to DinoV/PTVS
that referenced
this issue
Apr 15, 2016
DinoV
pushed a commit
to DinoV/PTVS
that referenced
this issue
Apr 15, 2016
Add a Extract Method suggested action and include a preview of the new change Add a PreviewChangesService for creating a preview text view based upon a set of changes Fix microsoft#186 Special case checking for REPL buffers that start with a $ and don't provide quick info. Unfortunately we have to do that because the REPL window input kind doesn't change until we have a complete input Fix microsoft#792 Clean up our BufferParser/AnalysisEntry/TextView tracking so that we can support this. We no longer attach any properties to text buffers at all. Instead we always resolve from textview and/or filename into a ProjectAnalyzer and then get the buffer from there. We now flow TextView's where they're available into our analyzer. There's only really 3 spots where we don't have that full context: Outlining regions and proximity info via the old IVsLanguageInfo interfaces. Add support for CommonPackage.GetActiveTextView so that we can find the correct active text view for diff windows. This is used all over the place to find the text view when we're doing various editing commands like extract method, find all refs, goto def, etc... Update Extensions to add various helpers which deal with the caret within a projection buffer.
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(Definitely VS 2015, haven't checked VS 2013 but I doubt it's changed there.)
The Extract Method command is no longer visible on the editor context menu.
It appears under Edit -> Refactor, and the keyboard shortcut still works. Users can use Tools -> Customize to add the item to
Editor Context Menus | Code Window- "Extract Method" is found under Edit in "Add Command".The text was updated successfully, but these errors were encountered: