Q:    Are the original Java files altered in any way?

A:    Your existing code is left completely intact.  The new VB or C# files are written to the new location that you specify.

Q:    What is the conversion accuracy?

A:    Our accuracy is the highest in the industry, but there will be significant adjustments required for all but the most trivial conversions.  There are no direct equivalents for some aspects of Java.  Read the rest of the FAQ to get an idea of a few things that are not converted.  Java to VB & C# Converter is intended to reduce the amount of work you'll have to do to convert code to VB or C#, but it is just the first step.

 

Q:    What are the most common adjustments necessary after conversion?

A:

●  Most Java platform or library function calls are not converted. However, we do convert a subset of the Java string, keyboard I/O, math, and utility function calls.  Also, many Java container classes are converted to .NET container classes.

●  VB.NET does not allow assignments within expressions, but Java does (e.g., while ((x = y()) > 0) assigns a value to x as part of an expression). Java to VB & C# Converter will convert simple assignment cases (e.g., x = y = z or x = y++), but will mark other more complex cases with a "ToDo" comment. You must manually adjust these.

●  Some reference type comparisons are converted, but you will need to manually change some equality symbols to "Is". The VB.NET compiler makes these adjustment requirements obvious.

●  Java's workaround for event handling has no direct equivalent in .NET's simple and concise event handling model.

●  Java wildcard generics have no equivalent in VB or C#, unless used in a method declaration parameter list.

●  Java local classes or anonymous classes cannot be declared within methods in VB or C#. These are marked with a comment.