No. VB is a much looser language than C#. In VB, you aren’t required to convert types when making assignments, define variable types, or even variables themselves. A lot of your conversion accuracy will depend on the quality of the VB code being converted, though the converter will do what it can to help compensate.
Currently upgrades are free, but we may start charging for upgrades in the future.
Yes, there is email support for no charge. Emails are answered within 24 hours, often much sooner.
We’re confident in our product and offer a generous refund policy. If you are unsatisfied with the product you may request a full refund with no time limitations, and no hassle.
The Trial Version expires in 15 days and is limited to 2000 lines of code.
Not directly, but Visual Basic 6 projects can be upgraded with the VB6 Upgrade Wizard in Visual Studio.Net and then run through the converter. Make sure the upgraded project compiles successfully in VB.Net before attempting to convert it to C#.
You can convert VB.Net 2005 web sites by making them Web Application Projects. Web Application Projects is an add on to Visual Studio 2005 that creates project files (.vbproj) for VB.Net 2005 websites.
Once you make your website a Web Application Project, you can select the .vbproj file to convert. You can find out more about Web Application Projects here:http://www.microsoft.com/downloads/details.aspx?familyid=8B05EE00-9554-4733-8725-3CA89DD9BFCA&displaylang=en
Use the project converter instead of the snippet converter: To do an accurate conversion, the project file contains important details, such as project level imports and references, which are critical to accurate conversions.
For example, without being able to unambiguously resolve all identifiers, it is difficult to fix casing errors (since VB is case insensitive) or determine if () should be converted to () or .
In addition, automatic C# compiler error fixing isn’t available in snippet conversions, since most won’t compile successfully even in VB without proper imports and references defined.
Prepare your VB.Net code: Make sure your VB.Net project compiles successfully, and all project references are valid.
Heed any VBConversions high-severity warnings issued before the conversion, and change the VB.Net code as suggested before reattempting the conversion.
Hold off on directly editing the C# code as long as possible: For any C# compiler errors encountered after the conversion, try to change the VB.Net code and reconvert rather than editing the C# code directly.
A unique feature of VBConversions is that it will fix most C# compiler errors automatically after the conversion by invoking the C# compiler and analyzing the error messages. However, this process can be cut short by an unexpected C# compiler error. You will have the best results if you can edit your VB.Net code to avoid the error and reconverting.
Accuracy: VBConversions analyzes your code in-depth to provide the most accurate conversion possible, as well as automatically fixing most C# compiler errors after conversion. Your code is also improved by replacing On Error Gotos with Try/Catch blocks, removing unnecessary ByRef parameters (common in upgraded VB6 projects), as well as many other improvements.
Configurability and Ease of Use: There are also dozens of configurable options to make the conversion fit your needs, though you don’t have to change any, and there is plenty of feedback along the way to make your conversion as easy as possible.
Support: If you ever want a feature added to meet your needs, or have a problem to report, let us know and a new custom build will be sent to you. These are often done within 1-2 days, and many new features released are just because one person asked for it.
All project types: Windows Forms, Console, Windows Service, Web Forms, Web Control, Windows Control, Class Library, Silverlight, and Compact Framework projects.