"If not for Tangible's Instant C# and Instant VB
code conversion tools, I might still be sitting here pounding out the dual
C# and VB samples used throughout the book."
– Julie Lerman, Best-selling author
Saves valuable time
Accurate and comprehensive
Easy to use
Safe - your code never leaves your machine
Responsive customer support
15 day money-back guarantee
Flexible - converts snippets, files, projects, solutions, and folders from VB.NET to C#
Fast - tens of thousands of lines converted from VB.NET to C# per minute
Helpful conversion comments
Excellent educational tool for VB developers learning C#
Numerous conversion and formatting options
10 Second Preview
VB.NET to C# Indexer Conversion:
VB.NET to C# Lambda Conversion:
Conversion of Legacy String Functions to C#:
VB.NET to C# LINQ Conversion:
*Scroll right to see Instant C# screenshots
Q: Are the original VB.NET files altered in any way?
Your existing code is left completely intact.
The new C# project is output 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 adjustments required for all but the simplest conversions. 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 way to convert 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 - VB code within ASP.NET markup is 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 - the converter will sort out most cases, but some
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).
Project conversions never produce auto-generated files, such as the Resources.Designer.cs or Settings.Designer.cs files.
For .NET Core projects, these should be automatically re-generated (may require saving the resources or settings), but for .NET Framework projects, after conversion you will need to right-click on the
"Settings.settings" file within Visual Studio and select "Run Custom Tool" to force auto-generation of the Settings.Designer.cs code file.
Similarly, you will need to right-click on the "Resources.resx" file within Visual Studio and select "Run Custom Tool" to force auto-generation of the Resources.Designer.cs file.