Support VB.NET (.vb) language — files skipped during indexing

[Warda502]

What problem does this solve?

VB.NET (.vb) project files are completely skipped during indexing. The indexer reports 0 nodes for all .vb source files despite the project containing ~200+ .vb files with classes, functions, interfaces, and events. The project compiles and runs fine — the issue is purely on the indexing side: codebase-memory-mcp does not recognize .vb as a parseable language.

This means users with VB.NET codebases (still actively used in Windows desktop / WPF / WinForms / enterprise environments) cannot benefit from any of the 14 MCP tools — search_graph, trace_path, get_architecture, etc. — for their VB.NET source files.

Proposed solution

Add VB.NET to the supported languages list by vendoring a tree-sitter grammar for Visual Basic and wiring a VB extraction pass.

Tree-sitter grammar: https://github.com/CodeAnt-AI/tree-sitter-vb-dotnet

Required capabilities:

• Parse .vb files
• Extract Functions, Classes, Methods, Interfaces, Enums, Properties, Events
• Support Imports for module/namespace resolution (VB equivalent of using/import)
• Handle XAML code-behind partial classes (.xaml.vb)

No Hybrid LSP pass is expected initially — syntactic AST extraction would already be a massive improvement over the current zero-node outcome.

Alternatives considered

Users can fall back to grep/glob for searching .vb files, but this loses all structural querying (call graphs, trace_path, dead code detection, architecture overview) that makes codebase-memory-mcp valuable. Converting the project to C# is not a practical workaround for existing codebases.

Confirmations

• I searched existing issues and this is not a duplicate.

[DeusData]

Thanks for the well-scoped VB.NET request and for naming a candidate grammar. This is tracked as a 0.9.2-rc language-support enhancement. Before implementation we need to verify the grammar source, pinned revision, permissive license, generated C surface, and realistic extraction fixtures for classes, methods, interfaces, events, and common project layouts.