Roslyn: Cannot navigate to the symbol under the caret

[GerryGe]

Version Used: VS 2017 Professional Version 15.2 (26430.14) Release

Steps to Reproduce:

1. Go to Definition of Class "AbpWebApplication"

Expected Behavior:

Actual Behavior:
I can work on VS 2015 Professional Version 14.0.25431.01 Update 3.

[GerryGe]

Because of class AbpWebApplication is generic?

[Pilchie]

Yes. This is a dupe of https://github.com/dotnet/roslyn/issues/17360, which is fixed in the Visual Studio 2017 Preview version 15.3

[GerryGe]

@Pilchie Thanks.

[zeeshan-ahmad111]

I am facing the same problem in VS 2019 Professional.
Tried many things but nothing worked for me.
The Code compiles successfully.

[arjun-khadka]

Just delete .vs folder and open the solution again.

[rdijkstra]

Sorry, I deleted the .vs folder (AND I installed the compiler version 3.2.1) makes no difference!

[zeeshan-ahmad111]

These are the steps to resolve
1) Right click on "References" in the Solution Explorer
2) Select "Manage NuGet Packages"
3) Under the "Installed" tab search for "Microsoft.Net.Compilers"
4) Select "Microsoft.Net.Compilers"
5) On the side window of "Microsoft.Net.Compilers" click the update button

[rdijkstra]

Dear Replier,

thanks!

But... That is exactly what I did, and the installed version 3.2.1. of
the Windows.net.compilers and pushed the update button (the update
button is now greyed out, because there is now nothing to update... )

This, however, has no effect on the problem... I still can't use F12 to
navigate to the function definitions in de javascript of the .aspx files
(it DOES work with F12 the definitions in C# in the .cs files...)

--

met vriendelijke groet,

Rients Dijkstra
VeriDOP Software Services BV
e. [email protected]
m. 06 21 408 730

On 9-9-2019 08:37, zeeshan-ahmad111 wrote:
>

These are the steps to resolve

1. Right click on "References" in the Solution Explorer
2. Select "Manage NuGet Packages"
3. Under the "Installed" tab search fro "Microsoft.Net.Compilers"
4. Select "Microsoft.Net.Compilers"
5. On the side window of "Microsoft.Net.Compilers" click the update
   button

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/roslyn/issues/20779?email_source=notifications&email_token=AHPUEYZMQCJ726N27FRQNHLQIXVLTA5CNFSM4DSPAZW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6GMV3A#issuecomment-529320684,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHPUEY4GQYSEIM6SM34AS3DQIXVLTANCNFSM4DSPAZWQ.

[chatteberg]

I have a VB .NET 4.6.1 Windows Forms Application.
When I open it in VS2017, all works.
When I open it in VS2019, the following problems occur:

1. For references to functions in another file (references in same file work):
   Peek Definition doesn't work (respond)
   GoTo Definition pops error 'Cannot navigate to the symbol under the caret'
2. None of the 10+ Windows form designers can display the form, instead get the error 'The designer could not be shown for this file because none of the classes within it can be designed'. There are no other references or details in the designer error to indicate a problem.

The solution compiles without any errors.
When I close VS2019 and open up VS2017, it works with exact same files and solution.
I have de-installed both versions of VS and installed them again. No change.
I have removed '.vs' folder, cleaned solution, cleared symbol cache, checked NuGet packages (all current), and removed extra ' In VS2019, I can add a new form and the designer fails to work.
In VS2017, I can add a new form and the designer works.

[sharwell]

@zeeshan-ahmad111 @rdijkstra @chatteberg Can you file a new issue for what you observed? This is an old/unrelated/fixed bug.