[WIP Documentation] Compare the 3 different static ways

[GeorgeS2019]

Statically: By compiling a Java application into a .NET assembly using <MavenReference>, <IkvmReference> or ikvmc

• Libary assemblies can be referenced by any .NET application with a compatible target framework and platform. Types can be referenced by using the Java package name like a .NET namespace.
• Executable assemblies can be launched by specifying the class containing the main() method to execute at runtime when building using ikvmc.

[GeorgeS2019]

Ikvmc

• Single jar file
• jar file and class files to a single exe
• jar file to dll and class files to an exe

ikvmc [ options ] classOrJarfile [ classOrJarfile ... ]

options

classOrJarfile

Name of a Java .class or .jar file. May contain wildcards (*.class).

Note

When converting a Java application with ikvmc, for best results, list the jars on the ikvmc command line in the same order that they appear in the Java application's classpath.

[GeorgeS2019]

Questions for best results

Note for ikvmc

When converting a Java application with ikvmc, for best results, list the jars on the ikvmc command line in the same order that they appear in the Java application's classpath.

Note for IkvmReference

For best results, HOW TO List the jars on the ikvmc command line in the same order that they appear in the Java application's classpath.

[GeorgeS2019]

Ikvmc

Examples for listing the jars on the ikvmc command line in the same order as discussed above.

IkvmReference

Examples for listing the jars on the IkvmReference in the same order as discussed above.

MavenReference

This approach has an intrinsic way of listing the jars in the order as discussed above