VB.Net to C# Converter FAQ
What versions of Visual Studio do you support?
All versions: Visual Studio 2003, 2005,
2008, 2010, 2012, and 2013.
Why should I use VBConversions over other converters?
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.
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
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.
What types of VB.Net projects can be converted?
All project types: Windows Forms, Console, Windows Service,
Web Forms, Web Control, Windows Control, Class Library, and Compact Framework projects.
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#.
What's the Difference Between the Trial Version and the Full
The Trial Version expires in 15
days and is limited to 2000 lines of code.
Delivery, Refund /
Delivery: Immediately after purchase,
you will be emailed an unlock code which will turn the trial version into a fully registered version.
Refund Policy: No questions asked, unlimited time frame to return
We intensively tested 6 products...this is
absolutely the best tool for the job.
The Select Group
DTS Power Search
Search DTS packages across multiple servers at
once! Free download at