Convert VB.NET 2005 to C#.NET 2005

[yesufollower]

Is there a way to convert a VB.NET 2005 application to a C#.NET application? Thanks.

[Ed Poore]

There are a few VB -> C# converters out there. I don't know how much SharpDevelop's progressed, especially for .NET 2.0 but you may be able to convert the majority of it using this and then tweak the code manually. I'm afraid that's the only recommendation I have for .NET 2, I know of a few others for .NET 1 though. The most reliable method would be to convert it manually (unless it's several million lines long) :) Ed

[Joe Woodbury]

You are almost always better off doing such things manually. A construct that may be great in VB, could be a dog in C#. Another option is shove all the VB.NET stuff into it's own assembly and don't worry about converting it. Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke

[Daniel Grunwald]

Step 1: Ensure the VB app compiles with Option Strict and Option Explicit. Step 2: Use the automatic converter in SharpDevelop 2.0. (Project > Convert > From VB to C#) Step 3: Fix any compiler errors introduced by the conversion (e.g. error because of case-sensivity) Step 4: Carefully review the C# code

[mcljava]

I have been hearing years can I convert from xxx to C, C++, and now C#. Now the issue at hand, a VB .NET application to be converted to C#. My initial inclination is to address the question of what is gained by converting to C#? Don't get me wrong, I prefer any C variant to any VB variant. BUT with .NET the choice of language is really distilled down to what style you prefer most: C#, VB, J#, I even hear there is a Python for .NET. At the end of the day, unless you have a lot of spare time converting an application to another for the sake of changing styles and format is a dubious endeavor. IF however you have a real need such as your company has forbidden VB then I would lean toward rewriting. Code generators and converters are decent when you get then tuned but let's face it if the whole point of converting the app is to get it in C#, I would not trust that to a conversion process. Mike Luster CTI/IVR/Telephony SME

[mcljava]

I have been hearing years can I convert from xxx to C, C++, and now C#. Now the issue at hand, a VB .NET application to be converted to C#. My initial inclination is to address the question of what is gained by converting to C#? Don't get me wrong, I prefer any C variant to any VB variant. BUT with .NET the choice of language is really distilled down to what style you prefer most: C#, VB, J#, I even hear there is a Python for .NET. At the end of the day, unless you have a lot of spare time converting an application to another for the sake of changing styles and format this becomes a dubious endeavor. IF however you have a real world need such as your company has forbidden VB then I would definitely lean toward rewriting. Code generators and converters are decent when you get then tuned but let's face it if the whole point of converting the app is to get it in C# to improve the maintainability, I would not trust that to a conversion process. Good Luck Mike Luster CTI/IVR/Telephony SME

[Dave Doknjas]

There are a number of VB to C# converters out there, including ours (Instant C#). The code quality after conversion will be nearly identical to the code quality before conversion (after a few manual adjustments). David Anton www.tangiblesoftwaresolutions.com Instant C#: VB to C# converter Instant VB: C# to VB converter Instant C++: C# to C++ converter and VB to C++ converter Instant J#: VB to J# converter Clear VB: Cleans up VB.NET code Clear C#: Cleans up C# code

[angelagke]

here hav a useful website to convert either VB.NET to C#.NET or C#.NET to VB.NET. Try for it ;) http://www.developerfusion.com/utilities/convertcsharptovb.aspx[^] angela