Extremely responsive, personalized customer support
Easy to use
Produces helpful notes, warnings, and 'to do' comments
Excellent learning tool for those new to C#
Q: Is the original VB.NET project altered in any way?
Your existing code is left completely intact.
The new C# project is written to the new location that you specify.
Q: Do you guarantee a 100% complete conversion?
No. Our accuracy is very high, but there will be
some minor tweaks required in all but the simplest projects. Read the rest
of the FAQ to get an idea of a few things that are not converted.
Q: Does Instant C# convert VB6 projects to C#?
No. The most effective and safest way to get from VB6 to
C# is to first upgrade to VB.NET, and then use Instant C# on the resulting VB.NET code.
Q: How are classic VB.NET string functions handled?
By default, Instant C# converts them to
the closest .NET string method. You also have the option of leaving them as
calls to the Microsoft.VisualBasic namespace, if you are depending on some
of the strange quirks of the classic VB string functions.
Q: Is VB.NET code within ASP.NET files converted?
No. ASP.NET files, including vbhtml files ('razor syntax') are not converted.
Q: What are the most common adjustments necessary after conversion?
If the VB project did not have 'Option Strict On' set, then you'll
likely have a number of cases where different types are compared
with each other - these may need adjustment.
Although some On Error GoTo statements are
converted, some elements of classic VB unstructured error
handling (On Error Resume Next, On Error GoTo -1, etc.) are not
converted by Instant C#. These statements are marked as a
Instant C# converts the
Microsoft.VisualBasic members which have close .NET equivalents,
but some references to the Microsoft.VisualBasic
namespace are left intact (the code will compile via
explicit references to the .NET Microsoft.VisualBasic namespace).