_From @habakuk007 on January 29, 2016 13:23_
VB is compared to C# the advanced language - fully support it.
_Copied from original issue: Microsoft/vscode#2538_
I'd like to see Visual Basic .Net support in Visual Studio Code, too.
Of course including all the features it provides for C# development.
This would be awesome because there is no good working IDE for VB .Net next to Visual Studio, which is only running on Windows platform.
So this would be a major step to push VB .Net language usage, when you can use all supported platforms to develop with VB .Net.
:+1: for Vb. I also recommend a language neutral way of handling the msbuild project file for any .net language since the XML structure would be identical.
I'd love to see support for it as well. +1
Save developers who have to work with legacy code written in VB6 like myself.
Voting for this one. +1
I would like to see this as well! +1
It is a pity that VB is not supported. .NET Core supports it now, and considering the beginner-friendly and business-friendly nature of VB, it would be a great addition to omnisharp-roslyn and omnisharp-vscode.
What really missing is Debugger support especially since .NET Core 2.0 finally supports the VB language and offers a few templates.
+1, thumbs up, whatever is needed to get this implemented
+1
I was going to ask, is vb.net supported ? But seeing this thread, I have to assume this extension only supports C# and not vb.net . I think that is going to prevent me from switching for full visual studio to visual studio code
+1 :+1:
Does up-voting increase the likelihood of this feature being implemented? What do we, as users of OmniSharp, need to do in order to draw attention to this feature?
Sending them money is probably the most effective way of getting their
attention. Next would be introducing vscode to fellow VB coders and have
them post on this thread of their genuine desire to have the basic features
of intellisense and live debugging added to vscode
On Tue, Sep 18, 2018, 19:25 Ethan Lindemann-Michael, <
[email protected]> wrote:
Does up-voting increase the likelihood of this feature being implemented?
What do we, as users of OmniSharp, need to do in order to draw attention to
this feature?—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/OmniSharp/omnisharp-vscode/issues/25#issuecomment-422591768,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKITvYopiWUN902XagLXTONXzvJoFI9Aks5ucYDNgaJpZM4HP1W2
.
Would it make a difference if donations were sent to the omnisharp team for VB.NET integration with VSCode? @david-driscoll @DustinCampbell
This feature request was added to the Future milestone which is no longer active. Should it be moved to the backlog milestone?
You may want to try CS-Script VS-Code extension. It supports VB.NET since Apr 2018:

Upvoted, would love to use VB.NET on VSCode.
You may want to try CS-Script VS-Code extension. It supports VB.NET since Apr 2018:
Apparently, it doesn't work for me at least. CS-Script isn't that good at supporting VB.NET. Also, no syntax highlight fix...
Could you please elaborate?
No VB yet?? Do it!
I am not sure I understand what you are trying to say.
VB is supported by CS-Script plugin since Apr 2018. VSCode does Syntax highlight and CS-Script does intellisense, execution and debugging. The screenshot (two posts above) illustrates it.
So "doesn't work for me" and "do it" without any details do not help the discussion.
CS-Script does not have outline on VB files...
@oleg-shilo Thanks for the extension. It's a great way to execute C# and VB like Python. Does it work with VS Projects too?
If you mean Visual Studio then yes.
If you mean opening .csproj file in VSCode. Then NO :(
CS-Script follows Python approach. A single script file is a complete expression of all runtime dependencies: f.cs files, assemblies and packages. So .csproj does not have role in any scripting scenario.
CS-Script does not have outline on VB files
CS-Script does not implement outlining at all but only intellisense operations, execution and debugging integration. Outlining is the responsibility of IDE. You can use CodeMap extension. It supports 10 languages including C#. But for VB you will need to extend it:
https://marketplace.visualstudio.com/items?itemName=oleg-shilo.codemap
Closing this as by design. The C# plugin is for C# and there will be some future investments that may allow for a proper VB plugin to be built that uses the same core Roslyn-based infrastructure. But there aren't any plans to incorporate a full fidelity VB experience into the C# OmniSharp experience.
@cartermp Could you please clarify a bit what the current status of Visual Basic is for OmniSharp (and/or VS Code):
Most helpful comment
I'd like to see Visual Basic .Net support in Visual Studio Code, too.
Of course including all the features it provides for C# development.
This would be awesome because there is no good working IDE for VB .Net next to Visual Studio, which is only running on Windows platform.
So this would be a major step to push VB .Net language usage, when you can use all supported platforms to develop with VB .Net.