-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Visual Basic Support? #236
Comments
Yeah, it's a little frustrating re-installing the latest versions of Visual Studio 2015 hoping VB will have vNext templates with no luck. |
ASP.NET 5 is C# only at this point and that will not change before we RTM. We plan to have extensibility points so other languages like VB, F#, etc can be added via the form of a support package or such. |
Thanks for the response. It's good to know the longer-term strategy so I can adjust my plans. Also great to hear F# is in the works too. |
@matthewhancock I don't think you understood the answer. Neither F# nor VB are "in the works", at least not by Microsoft. All he said was that there are plans to have extensibility points so that "someone" could theoretically develop support for these languages. |
Hey everyone, good news! We've announced plans to support VB in ASP.NET 5 / DNX! Read more on the official blog post: http://blogs.msdn.com/b/webdev/archive/2015/04/23/making-it-better-asp-net-with-visual-basic-14.aspx Stay tuned for updates. |
Totally awesome! I will be using it! |
Why would you guys ever drop support for VB.net? Very strange.... |
Maybe the VB Developers, are not that active writers in the net, like their C# friends, but that doesn't mean, that they are not filling a huge number of places in corporate chairs. |
See aspnet/dnx#1706 |
- Replace hardcoded port "12345" with dynamic ports to improve test reliability - Addresses #3063 - Depends on aspnet/Hosting#1387
I was interested in trying out vNext with VB.NET? It seems to be promoted on most of the news but I don't see anything but C#. What's the latest news?
The text was updated successfully, but these errors were encountered: