CODEWITHSUNDEEP
c#
user595234
user595234

Reputation: 6259

MS Visual Studio IDE tip

As a java developer, I am required to work on C# .

I am familiar with Eclipse IDE. In the MS Visual Studio 2010 Ultimate, how to do the similar ?

  1. If I use F12 to see the difinition, then how can I go back to the original file ?

  2. For an interface, how can I see all classes implementing this interface or method ? In the Eclipse, we just use CTRL+K.

Upvotes: 6

Views: 176

Answers (5)

Steve
Steve

Reputation: 216333

Not sure for the second request however:

  1. CTRL+- go back to the previous position
  2. CTRL+K, R find all references

Upvotes: 2

NiK
NiK

Reputation: 1857

For the first one, F12 will take you to the definition...where as Ctrl + - (minus) ....will take you back to where you were before...

As other ppl mentioned the second case is not supported... Here is a list of Pre-Defined keyboard shorcuts for Visual Studio 2010...that can be useful to you...

Upvotes: 0

qJake
qJake

Reputation: 17139

1) If your mouse has a "Back" thumb button, you can typically use that to navigate backwards. Otherwise, bind a keyboard shortcut to "View.NavigateBackward" (Edit: The default key binding is Ctrl + -). Or click this button:

2) This isn't possible without an extension of some kind, Visual Studio doesn't support this out of the box. The best you could do is "Find All References" on the interface, and the results of that should include every class that implements that interface.

Upvotes: 4

Irfan
Irfan

Reputation: 2771

After hitting F12 and naviating to the function definition, you can use Ctrl+TabKey to go back the source file.

Moreover, for a detailed list of keyboard shortcuts of VS 2010 see this list.

Upvotes: 0

Joel Coehoorn
Joel Coehoorn

Reputation: 416111

  1. Right click, "Go to Definition"
  2. Not supported, because it's a bad feature that leads to bugs. You shouldn't use it. The reason? It's likely that important projects that have types that implement an interface will not be loaded, and so this would lead to a false sense that you've touched every implementer. Most of the time when you want to do this, you're looking the wrong direction up your inheritance tree.

Upvotes: 1

Related Questions