In its move to the ASCII text file, cross-platform .NET Core, Microsoft can support Visual Basic within the future .NET five and is increasing the programming language’s supported application sorts to assist VB developers migrate their code, however noted we don’t arrange to evolve Visual Basic as a language. The distended project sorts to foster a move to the new framework were in response to client feedback, aforementioned Microsoft, that noted blessings of the language like stability.
The enlargement of supported project sorts can facilitate VB coders move their existing applications to .NET Core/.NET five and leverage cross-platform practicality and options like higher performance, side-by-side preparation, and new API enhancements. The .NET Core evolution is presently at version three.1, with the unifying .NET five planned for Gregorian calendar month. Microsoft declared that with .NET 5, VB’s supported project sorts can increase on the far side category Library and Console applications to conjointly support:
Windows Forms WPF Worker Service ASP.NET Core net API
However, it had been the warnings concerning future support and evolution of the language that caught the eye of multiple developers United Nations agency commented on the post that garnered a bizarrely high variety of comments (39 and investigating steady at press time).
Going forward, we tend to don’t arrange to evolve Visual Basic as a language, the .NET team aforementioned. Future options of .NET Core that need language changes might not be supported in Visual Basic. Because of variations within the platform, there’ll be some variations between Visual Basic on .NET Framework and .NET Core.
Microsoft conjointly noted that a VB app migration to .NET Core isn’t essentially within the plans for all developers, because it works fine with the Windows-only .NET Framework which is able to be supported as long as Windows is. If your application uses technologies that aren’t supported on .NET Core, like WebForms, progress or WCF, you would possibly need to remain on .NET Framework as a result of porting would force work to maneuver to newer technologies the post aforementioned.