CODEWITHSUNDEEP
visual-studiovisual-studio-2008visual-studio-2005
nick_alot
nick_alot

Reputation: 3012

Visual Studio ‘Go To Definition’ menu option behaviour - Why is it inconsistent between C# and VB projects

When developing in a VS2005+ with C# project and I right click on a framework method/property/type and select ‘Go To Definition’, by default we get a new locked tab with code that has been generated from the framework, labelled appropriately [from metadata].

However when we do the same in a VB.NET project, you get taken to a new tab with the relevant Object Browser view.

This has always struck me as peculiar and was hoping there was a good reason behind it. IMO the object browser is nicer.

Is there a logical reason for the difference in default visual studio behaviour? If so, what is it?

Upvotes: 4

Views: 2478

Answers (2)

DenzicW
DenzicW

Reputation: 1

You can install Resharper for this.

It'll allow you to choose the default behavior when clicking the "go to definition".

Upvotes: 0

JaredPar
JaredPar

Reputation: 754665

It's a choice each team made based on what they believe their respective customers wanted to see. VB users have a historical attachment to the object browser and many VB features are integrated into it (Go To Def being one of them). C# made a switch in VS2005 to generate metadata on the fly for their version of GoTo def because they believed their customers would like the behavior better.

Upvotes: 6

Related Questions