anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE]:Add Visual Basic .NET (VB.NET) Language Server Protocol (LSP) Support #6878

New Issue
Open
opened 2026-02-16 18:05:30 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:05:30 -05:00
Owner
Copy Link
Copy Source

Originally created by @k-wakamatsu-tms on GitHub (Jan 19, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

What do you want to change or add?

I would like to request Language Server Protocol (LSP) support for Visual Basic .NET (VB.NET) in OpenCode, similar to the existing C# LSP integration.

Currently, OpenCode provides built-in LSP support for C#, but .vb files are not recognized by any language server.
Adding VB.NET LSP support would allow OpenCode to be used effectively in mixed-language .NET codebases and in legacy enterprise environments where VB.NET is still actively maintained.

Why is this important / What are the benefits?

  • Large existing VB.NET codebases
    VB.NET is still widely used in long-lived systems such as ASP.NET WebForms, WinForms, and internal enterprise tools. Many teams maintain VB and C# side by side.

  • Roslyn-based implementation is technically feasible
    VB.NET is fully supported by the Roslyn compiler platform, which already provides semantic analysis, diagnostics, and symbol resolution. This makes implementing an LSP server for VB.NET technically viable and aligned with how C# LSP works.

  • Parity with C# experience
    Developers expect the same level of language tooling for VB as for C# in modern editors. Without LSP support, VB projects are significantly disadvantaged in OpenCode.

  • Better adoption in enterprise / legacy modernization projects
    OpenCode would become more attractive for teams modernizing legacy .NET systems who cannot immediately migrate away from VB.NET.

Suggested implementation (optional guidance)

  • Provide a built-in VB.NET LSP configuration, similar to the existing C# setup
  • Or allow an officially documented custom LSP example for .vb files (command, file extensions, workspace handling)
  • Even partial support (diagnostics + basic navigation) would be highly valuable as a first step
Originally created by @k-wakamatsu-tms on GitHub (Jan 19, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request ### What do you want to change or add? I would like to request **Language Server Protocol (LSP) support for Visual Basic .NET (VB.NET)** in OpenCode, similar to the existing C# LSP integration. Currently, OpenCode provides built-in LSP support for C#, but `.vb` files are not recognized by any language server. Adding VB.NET LSP support would allow OpenCode to be used effectively in mixed-language .NET codebases and in legacy enterprise environments where VB.NET is still actively maintained. --- ### Why is this important / What are the benefits? * **Large existing VB.NET codebases** VB.NET is still widely used in long-lived systems such as ASP.NET WebForms, WinForms, and internal enterprise tools. Many teams maintain VB and C# side by side. * **Roslyn-based implementation is technically feasible** VB.NET is fully supported by the Roslyn compiler platform, which already provides semantic analysis, diagnostics, and symbol resolution. This makes implementing an LSP server for VB.NET technically viable and aligned with how C# LSP works. * **Parity with C# experience** Developers expect the same level of language tooling for VB as for C# in modern editors. Without LSP support, VB projects are significantly disadvantaged in OpenCode. * **Better adoption in enterprise / legacy modernization projects** OpenCode would become more attractive for teams modernizing legacy .NET systems who cannot immediately migrate away from VB.NET. --- ### Suggested implementation (optional guidance) * Provide a **built-in VB.NET LSP configuration**, similar to the existing C# setup * Or allow an **officially documented custom LSP example** for `.vb` files (command, file extensions, workspace handling) * Even partial support (diagnostics + basic navigation) would be highly valuable as a first step
yindo added the discussion label 2026-02-16 18:05:30 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#6878
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?