I am willing to contribute in taking VB.NET to ASP.NET MVC Core

[VBAndCs]

Hi.
I want to use VB.NET in ASP.NET MVC Core. I'm tired of waiting, so I am willing to contribute in writing/modifying VB razor (.vbhtml files) and any other necessary tasks needed to make it work in MVC Core.
I need a ToDo list, and some guideness to where to start.
Thanks.

[hishamco]

This seems not an easy task, I already have this in my mind from the beginning, but while Razor written for C# in ASP.NET Core, the solution is write template language to compile `.vbhtml`` files

BTW VB.NET is supported in ASP.NET Core, but it's not supported in views

[VBAndCs]

This seems not an easy task, I already have this in my mind from the beginning, but while Razor written for C# in ASP.NET Core, the solution is write template language to compile `.vbhtml`` files

BTW VB.NET is supported in ASP.NET Core, but it's not supported in views

I think it is not that hard. Every thing is already done in ASP.NET MVC 5 for vbhtml files and just copy it to the dot core project. I need a little push about what files need to be modified in c# asp.net project and I wiil convert the parser and any related conponents to work on vb syntax

[hishamco]

I don't think so, there 're many things changed in ASP.NET Core from the previous version, may be looking to the current Razor implementation is better

[VBAndCs]

No problem . I will start with the current C# razor and change the CSharp parser to Vb parser which is already written for asp.net 5. There will be changes in the editor / deugger also, and of corse the project template. I asked for guideness becuase the team is aware of all other spots that need modifications.

[hishamco]

Have a look to this issue #2738 it has a long discussion

[VBAndCs]

Saw it b4. Nothing new. MS thinks vb.net is less needed and doesn't want to spend money and waste resources on it. No real technical issues prevent Vb.net from moving to dot core.
So, I can solve the money and resources issue by assigning myself to this task :) I just want some guidelines not to go through all unnecessary parts of the project.

[kierenj]

I would guess (based on comments that hishamco kindly linked, like this one: #2738 (comment)) that is is a big job with plenty of technical issues (read: design and development to do), and that writing a "todo list" for you to pick up would be the result of many hours or days of discussion/work. Once it's down to a simple todo list, I'd imagine it would be fairly straightforward.

That issue seemed to point at some good starting points..

[VBAndCs]

@kierenj
I don't want to reinvent the wheel. Both VB Razor and C# razor use Roslyn to parse, compile and debug. This means I will not rewrite the compiler here. The task is to replace all parts that deals with c# syntax with those dealing with VB syntax. And I am not expecting to finish this in a week or two. I can give this task up to 6 months if necessary. So, give me a place to start, because when I looked at C# Razor source I couldn't find the C# parser! It seems that the project uses an internal sdk that I can't find its source! I don't want to go back to ASP.NET 5 and reinvent the wheel!
So, If ASP team cares, please show me the path, so I can start walking!

[hishamco]

I looked at C# Razor source I couldn't find the C# parser!

MVC is using Roslyn with C# infrastructure behind the scene

[Eilon]

Hi, the work to add support for VBHTML is enormous - that's one of the reasons that it is not supported in ASP.NET Core. But the work to maintain it is also substantial. As the VB language evolves, and as ASP.NET Core / Razor requirements and features evolve, the cost of having support for two languages takes away time that can be spent on other features, fixes, and enhancements (this includes ancillary things such as documentation, performance work, etc.).

So for those reasons, while we appreciate the willingness of people to contribute such a feature, it is not a feature we can accept at this time.

[VBAndCs]

@hishamco @kierenj @Eilon @shanselman
I want to simplify the problem of vbhtml, by using a code behind file.. suppose we have this cshml file:

@model IEnumerable<MvcMusicStore.Models.Genre>
@{
    ViewBag.Title = "Store";
}
<h3>Browse Genres</h3>
<p>
    Select from @Model.Count()
genres:</p>
<ul>
    @foreach (var genre in Model)
    {
        <li>@genre.Name</li>
    }
</ul>

I want to write the vbhtml file as:

<CodeBehind ClassName = "View1Code" FileName= "View1.vb"/>
<h3>Browse Genres</h3>
<p>
    Select from @ModelCount genres:
</p>
<ul>
    @Genres
</ul>

and view1.vb:

   Friend Shared Class View1Code
          Dim Model As IEnumerable(Of MvcMusicStore.Models.Genre)

    Public Sub New(model as IEnumerable(Of MvcMusicStore.Models.Genre)
          Me.Model = model
          ViewBag.Title = "Store"
    End sub
       
     Public Property Model.Count As integer = Model.Count( )

     Public ReadOnly Property Model.Count As String 
           Get
                Dim s = "";
                For Each genre in Model
                         s += &"<li>{genre.Name}</li>{vbCrLf}"
               Next
               Return s
            End Get
     End Property

   End Class

1- This will eliminate the need for parsing, compiling and debugging the vbhtml file, because it only contains a static placeholders that will be replaced with the evaluated properties at runtime. This will leave this file as a prototype html file.

2- The code-behind file is a normal vb file which doesn't need any special treatment!
This allows to use this model to write a razor for F# or any other language without any further coding!

3- No new effort needed in every new ASP.NET Core version. Any change in other parts of the framework will not affect the way we write these razor pages.

4- This is a simple divide and conquer approach, which makes the problem too simple. We may need to write some longer code in the code behind file, but it is direct and most of it can be generated with snippets or code generators. On the other hand, the vbhtml file will be cleaner. The @variable parts can view the actual code in tool tips or in a peak definition window.

If some one is willing to help me do this, we can have VB razor up and running in a few days. My problem is that I am lost in the ASPNETCore source code, and even failed to build the project on my PC! I am not experienced in project templates, and can't integrate the vbthml file and its code-behind in the MVC project.
I can write parts of this works, put I can't put the whole parts together! So, I need help.

[hishamco]

FYI you can do this with current bits without .vbhtml extension
As I mentioned earlier ASP.NET Core supports VB.NET except for views

[hishamco]

Hope this sample https://github.com/DamianEdwards/AspNetCoreVbHybrid make you happy