In its move to the open-source, cross-platform .NET Core, Microsoft will support Visual simple in the upcoming .NET 5 and is widening the programming language"s supported application varieties to assist VB developers move their code, but noted "we carry out not plan to evolve Visual simple as a language."

The broadened project varieties to foster a move to the new framework were in solution to customer feedback, said Microsoft, which provided advantages that the language such as stability.

You are watching: Vb vs c# which is better

"We"ve heard your feedback that you want Visual an easy on .NET Core," stated the .NET team in a in march 11 blog article titled "Visual basic support planned because that .NET 5.0."

The growth of sustained project types will assist VB coders move their existing applications come .NET Core/.NET 5 and also leverage cross-platform functionality and also features such as better performance, side-by-side deployment, and brand-new API improvements.

The .NET Core development is at this time at variation 3.1, v the unifying .NET 5 planned for November. Microsoft announced that v .NET 5, VB"s supported project species will increase past Class Library and Console applications to likewise support:

Windows forms WPF Worker company ASP.NET Core net API

However, it was the warnings around future support and also evolution the the language that captured the fist of lot of developers who commented top top the post, which garnered an abnormally high number of comments (39 and counting stability at push time).

"Going forward, we execute not arrangement to evolve Visual straightforward as a language," the .NET team said. "This support language stability and also maintains compatibility between the .NET Core and .NET frame versions of visual Basic. Future attributes of .NET main point that require language transforms may no be sustained in intuitive Basic. early to differences in the platform, there will be part differences in between Visual straightforward on .NET Framework and .NET Core."


Microsoft also provided that a VB app migration come .NET core isn"t have to in the plan for all developers, together it works fine with the Windows-only .NET Framework, which will certainly be sustained as lengthy as home windows is.

See more: When Do Girls Stop Playing With Dolls ? Playing With Dolls

"If your application offers technologies that aren"t supported on .NET Core, choose WebForms, Workflow or WCF, you can want to stay on .NET Framework due to the fact that porting will require job-related to move to more recent technologies" the post said.

That aforementioned developer feedback in the post"s comments section ranged from worship for VB to confusion around what the notice means. One developer said:

It"s no April first is it? This short article basically division Microsoft"s promises in catalent Dollard"s article barely 4 months ago:

In that write-up (actually released Nov. 12, 2018, however updated Oct. 8, 2019), Dollard explained Microsoft"s "Visual an easy in .NET core 3" strategy and quoted parts of Microsoft"s .NET languages Strategy guidance such as:

"We will execute everything essential to store it a first class citizens of the .NET ecosystem." "We will save Visual simple straightforward and approachable." "We will store a focus on the cross-language tooling experience, recognizing that plenty of VB developers also use C#." "We will emphasis innovation ~ above the main point scenarios and also domains wherein VB is popular."

it wasn"t clear what assures in that article were allegedly damaged with this week"s news as asserted in the reader comment, yet it nevertheless included to the confusion and also uncertainty among some developers about VB. Because that example, one developer commented:

i did not clearly understand the post. Native one next it said that is stable and use by plenty of developers and will be sustained in .net core yet from other side said that "Going forward, we do not plan to evolve Visual straightforward as a language." have the right to anyone in simple words explain if us can continue feel comfortable with VB.NET ? Shall we forget and also start turning to c#?

The .NET team didn"t seem to think so, ending its announcement with: "Visual basic is a an excellent language and a productive breakthrough environment. The future of Visual straightforward will encompass both .NET Framework and .NET Core and also will emphasis on stability, the applications types detailed above, and also compatibility between the .NET Core and also .NET framework versions of visual Basic."