Decompile uses C# syntax for Visual Basic projects resulting in broken navigation

[davkean]

Imports System.Windows.Forms

Module Module1
    Private ReadOnly _CF_UNICODE As String = DataFormats.UnicodeText ' <- Decompile this

End Module

Expected: For the file to be decompiled in VB and to navigate to UnicodeText
Actual: The file is in C# syntax and it fails to navigate

Copied from original issue: dotnet/project-system#3519

[sharwell]

Possible duplicate of #25159

[sharwell]

📝 The disassembler does not support VB as an output language. When this experimental feature is enabled, the target of a metadata navigation is expected to show disassembled C# code currently. #24349 is a higher-level issue to improve this experience.

[davkean]

Even if it was C#, I would still expect navigation to work, which it does not.

[CyrusNajmabadi]

What i'm not quite understanding is why we're creating a VB project to put this decompiled C# file into. Why not create a C# project instead? Then things should work properly.

[CyrusNajmabadi]

Here's an example of the problem:

A VB project for System.Runtime was created, but all the code is C#, so literally all IDE features are completely broken. Basic classification isn't even there. I can totally understand not supporting decompilation into VB since we just don't have that. But given that constraint, we should not be generating a VB project and placing the code into that.

[CyrusNajmabadi]

Looks like a dupe of #26329

[sharwell]

Duplicate of #26329