CODEWITHSUNDEEP
vb.netenumsvisual-studio-2015intellisense
ChrisA
ChrisA

Reputation: 4193

Is VS2015 intellisense broken with enums?

Just upgraded from VS2013 to VS2015 Enterprise Update 3 and discovered that intellisense seems broken with enums.

With VS2013, typing space after, for instance:

dim myEnum as MyEnumType =

... would immediately give a choice of enum values of the correct type.

This was also true with more complex situations, where, when choosing from a number of overloaded versions of a method, you could down-arrow through the overloads till you got to the right overload, then type space again, and it would give you a choice of the right enum values of the correct type, for the argument you had got to in the list.

Here's what VS2013 did, for instance:

enter image description here

However, this is the VS2015 equivalent, on the exact same line of code, after scrolling through to the correct overload:

enter image description here

As you can see, it gives a completely wrong list of possible options.

There was a similar problem with a previous version of Studio that eventually got fixed after the whole community howled in pain.

It seems to be back with VS2015 - a significant retrograde step. Now you have to know the exact type it's expecting before it will give you options.

A similar issue seems to have been reported a year ago re the Community Edition but it, or a more subtle version of it is clearly also affecting Update 3 of Enterprise.

Is there any way to reproduce the Common/All tabs behaviour of VS2013?

Edit: here are my selected options:

enter image description here

They're the same as I had in VS2013.

Upvotes: 0

Views: 229

Answers (1)

Sehnsucht
Sehnsucht

Reputation: 5049

What the intellisense shows is the list of member according to the current signature (or what the compiler thinks it could be), not according to the overload tooltip.

For example see this intellisense/overload demo
It shows the same overall behaviour as in your post.

But to obtain it, after having written the comma after "caption" I changed the current overload tooltip manually using up/down arrow on keyboard.

Note, it was not mandatory to change it manually even without that it was proposing me some overload which takes an IWin32Window for first argument even with an already present string as first argument

Then I pressed space and the intellisense showed what is appropriate given the context not the tooltip.

In your post we can see it's not the same overload in both screen.
I can't say for sure it is what happened for you (given I changed the overload tooltip on purpose) but if I had to bet, I would go that way.

Upvotes: 1

Related Questions