Based on my experience, I advise caution – though acknowledging that the converter does an amazing job, and is free and open source. I tried it, on a moderately-size VB DLL project.
Still, if converting a project is just a right-click in Visual Studio, you might as well do it, right? Even Visual Basic 6.0 applications still run, though you might find it convenient to keep an old version of Windows running for the IDE. Note though that Visual Basic is still under active development and history suggests that your Windows VB.NET project will continue running almost forever (in IT terms that is). Microsoft has stated that “with regard to the cloud and mobile, development beyond Visual Studio on Windows and for non-Windows platforms, and bleeding edge technologies we are leading with C#.” The Xamarin framework can use VB to some extent, but it is primarily a C# framework.NET Core was developed first for C#. Why would you do this though? There are several reasons, the foremost of which is cross-platform support. You can also find this on the Visual Studio marketplace. The SharpDevelop team has a nice tool for this, CodeConverter, which promises to “Convert code from C# to VB.NET and vice versa using Roslyn”. Some years later, I wondered how easy it is to convert a VB project to C# using Roslyn. NET compiler platform, one of the features described was the ability to take some Visual Basic code and “paste as C#”, or vice versa. When Microsoft first started talking about Roslyn, the.
0 kommentar(er)
