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

Any plans to support VB? #171

Closed
Nukepayload2 opened this Issue Feb 27, 2018 · 8 comments

Comments

Projects
None yet
7 participants
@Nukepayload2

Nukepayload2 commented Feb 27, 2018

Are there any plans to support VB?
I want to rewrite some of my old WebForm VB projects to modern MVC websites. Compared with asp.net MVC 4, Blazor is closer to WebForm, because events can be handled in .NET codes rather than Javascript.
With VB+Blazor support, I can reuse more VB codes during the project upgrade.

@SteveSandersonMS

This comment has been minimized.

Show comment
Hide comment
@SteveSandersonMS

SteveSandersonMS Feb 27, 2018

Member

In the long term we might well do, but for this first experimental phase we're keeping our project scope focused and are only looking at C# right now. Hope that's OK!

Member

SteveSandersonMS commented Feb 27, 2018

In the long term we might well do, but for this first experimental phase we're keeping our project scope focused and are only looking at C# right now. Hope that's OK!

@jesperhoy

This comment has been minimized.

Show comment
Hide comment
@jesperhoy

jesperhoy Jul 24, 2018

This thing (Blazor) sounds absolutely amazing - if only it supported VB.NET.

I have no problem with C# in general - but because we have a huge code base in VB.NET it is just not practical for us to move everything to C#.

And if I have to use one language on the server (VB.NET) and another for the client (C#) - then I might as well use one of the established and proven JS frameworks (Angular, React, Vue) + TypeScript since I loose the benefits of code re-use anyway.

In the docs you write "the purposes of this initial experimental phase are to ... Gauge interest and to listen to feedback."

We are still a lot of VB.NET developers out here, and I am sure that the "interest" you are looking for would increase if you prioritized VB.NET support.

Blazor with VB.NET would allow us to move our VB.NET WinForm based U.I. stuff to the web so much faster and easier than anything else.

I for one would go into production with this immediately - if it supported VB.NET.

jesperhoy commented Jul 24, 2018

This thing (Blazor) sounds absolutely amazing - if only it supported VB.NET.

I have no problem with C# in general - but because we have a huge code base in VB.NET it is just not practical for us to move everything to C#.

And if I have to use one language on the server (VB.NET) and another for the client (C#) - then I might as well use one of the established and proven JS frameworks (Angular, React, Vue) + TypeScript since I loose the benefits of code re-use anyway.

In the docs you write "the purposes of this initial experimental phase are to ... Gauge interest and to listen to feedback."

We are still a lot of VB.NET developers out here, and I am sure that the "interest" you are looking for would increase if you prioritized VB.NET support.

Blazor with VB.NET would allow us to move our VB.NET WinForm based U.I. stuff to the web so much faster and easier than anything else.

I for one would go into production with this immediately - if it supported VB.NET.

@Andrzej-W

This comment has been minimized.

Show comment
Hide comment
@Andrzej-W

Andrzej-W Jul 24, 2018

I fill your pain - we have desktop application written in C++. Do you already have WebAPI service written in VB? If not, it is time to forget VB and rewrite everything in C#. I don't know your application but I think that if you want to move VB.NET WinForm application to the web you have to rewrite almost everything. Of course you can have some business logic which is directly transferable to the web. You can try this http://converter.telerik.com/ to translate small snippets of your code from VB to C#.

Andrzej-W commented Jul 24, 2018

I fill your pain - we have desktop application written in C++. Do you already have WebAPI service written in VB? If not, it is time to forget VB and rewrite everything in C#. I don't know your application but I think that if you want to move VB.NET WinForm application to the web you have to rewrite almost everything. Of course you can have some business logic which is directly transferable to the web. You can try this http://converter.telerik.com/ to translate small snippets of your code from VB to C#.

@danroth27

This comment has been minimized.

Show comment
Hide comment
@danroth27

danroth27 Jul 24, 2018

Member

@jesperhoy Blazor runs on a WebAssembly based .NET runtime, which runs normal .NET assemblies. So if you can compile your VB to .NET Standard libraries I believe they should work in a Blazor app. The Razor syntax (.cshtml) used to author the component rendering logic is C# based, and there is no plans to change that, but all of the rest of your app logic I believe could be written in VB.

Member

danroth27 commented Jul 24, 2018

@jesperhoy Blazor runs on a WebAssembly based .NET runtime, which runs normal .NET assemblies. So if you can compile your VB to .NET Standard libraries I believe they should work in a Blazor app. The Razor syntax (.cshtml) used to author the component rendering logic is C# based, and there is no plans to change that, but all of the rest of your app logic I believe could be written in VB.

@jesperhoy

This comment has been minimized.

Show comment
Hide comment
@jesperhoy

jesperhoy Jul 24, 2018

@danroth27 - Thank you so much for responding.
That solution might just work for us!
I had all but written of Blazor - but now I'm all excited again :-) :-) :-)
I'll go give it a try...

jesperhoy commented Jul 24, 2018

@danroth27 - Thank you so much for responding.
That solution might just work for us!
I had all but written of Blazor - but now I'm all excited again :-) :-) :-)
I'll go give it a try...

@jesperhoy

This comment has been minimized.

Show comment
Hide comment
@jesperhoy

jesperhoy Jul 26, 2018

@danroth27 - I tested your suggestion - and it works very nicely indeed :-)

Now can you remove that "experimental" label please ? :-)

jesperhoy commented Jul 26, 2018

@danroth27 - I tested your suggestion - and it works very nicely indeed :-)

Now can you remove that "experimental" label please ? :-)

@Martin-Andersen

This comment has been minimized.

Show comment
Hide comment
@Martin-Andersen

Martin-Andersen Jul 26, 2018

Why support VB, its high time to move on

Martin-Andersen commented Jul 26, 2018

Why support VB, its high time to move on

@mixfede

This comment has been minimized.

Show comment
Hide comment
@mixfede

mixfede Sep 29, 2018

Please implement vb !!

mixfede commented Sep 29, 2018

Please implement vb !!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment