Roslyn: Visual Basic scripting

[hcd]

Hi,
When is the "official" VB scripting for Roslyn planned ? Right now, in the NuGet packages, even when using the prerelease package v2.0.0-beta3, there is no Visualbasic scripting included. If I get the sources from github and build it myself, the Visual basic scripting is there.
But it's not working correctly, eg. the "globals" feature doesn't work. It doesn't recognize nor compile when I use variables or methods that are defined in a class, and this class is passed via the globals argument when executing the script; This features works fine in C# though....

Kind regards,
Sven.

[DualBrain]

I wouldn't mind knowing the answer to this as well. :-D

[tmat]

The VB Scripting implementation is incomplete. As @hcd points out there are many issues to be addressed before we can consider it production quality. We would love to get VB Scripting out there but our focus is currently on other features. We would certainly accept any community contributions that get VB scripting to a better shape.

[tmat]

Currently open VB Scripting issues -- all are up-for-grabs, available for anyone to pick up:

https://github.com/dotnet/roslyn/issues?utf8=%E2%9C%93&q=is%3Aopen%20label%3AInteractive-ScriptingLogic%20label%3ALanguage-VB

[alcoda1]

I would like to integrate VB Scripting in our application (written in VB.NET of course) as well!

[Nukepayload2]

Any update on this issue? I want to develop a free plugin for MS Office that enables VB.NET interactive scripting in Excel.

[tmat]

@Nukepayload2 Unfortunately, no news in this area.

[ryan-bunker]

I'm interested in contributing to VB scripting, however the above list of issues seem very old and have almost no details about what each entails. Has it been entirely abandoned or is there still hope of completing the implementation? If there is still hope, where would be a good place to start?

[halittiryaki]

as already stated, please provide an updated list of open vb scripting support issues. thanks

[JustNrik]

any news?

[tmat]

We decided to focus our Visual Basic investments on improvements in tooling of existing language features and interoperability with new C# language features and .NET APIs. See The .NET Language Strategy for more details.