'Go to definition' doesn't work for component type name in C#

[DoctorKrolic]

Version used:
VS 2022 v17.3 Preview 1

To reproduce:

1. Create blazor server-side project
2. Go to App.razor
3. 'Go to definition' on MainLayout

Expected behavior:
I appear in MainLayout.cs

Actual behavior:
Nothing happens

Demo:

Additional context:
Very similar to #6399, but in #6399 the defenition is .razor file, while here - .cs file

[davidwengier]

Moving this to the compiler. This is failing because Roslyn go-to-def says we should be navigating to the class declaration for the MainLayout class in the generated file, but as there is no source mapping for the type name in that declaration, we can't map that span to the Razor document.

Similar to #7099 and #7097

[danroth27]

@chsienki Can we up the priority of this issue? I run into this issue frequently when I'm trying to walk users through the execution of a Blazor Web App and I want to navigate to the definition of the App component from the app.MapRazorComponents<App>() call in Program.cs.

[chsienki]

@jjonescz Can you take a look at this?

[davidwengier]

A quick note, this might need coordination/design with tooling. The issue is the class definition in Goo.razor.g.cs doesn't map to anything in Goo.razor, but thats because there is nothing for it to map to. If something hacky works, like adding a zero length mapping pointing to the start of the .razor file, that would be great, but otherwise we might need to come up with something special that tooling has explicit support for.