IKVM-8.8.0-bin-net6.0

# IKVM - Java Virtual Machine for .NET [](https://www.nuget.org/packages/IKVM) [](https://discord.gg/MpzNd5Tk8P) ## What is IKVM? IKVM is an implementation of Java for the Microsoft .NET platform. It can be used to quickly and easily: - Execute compiled Java code (bytecode) on .NET Framework or .NET Core - Convert bytecode to a .NET assembly to directly access its API in a .NET project These tasks can be done **without porting source code** to .NET. ### IKVM Components * A Java virtual machine (JVM) implemented in .NET * A .NET implementation of the Java class libraries * A tool that translates Java bytecode (JAR files) to .NET IL (DLL or EXE files). * Tools that enable Java and .NET interoperability * A full JRE/JDK 8 runtime image. ### Run Java Applications with .NET 1. **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`. 2. **Dynamically:** By running a Java application using the `java` executable inside of the JDK Runtime Image. The Java bytecode is converted on-the-fly to CIL and executed. The experience should be identical to a normal JDK. ## What IKVM is Not - A converter utility to transform Java source code to C# source code - A decompiler utitity to transform compiled Java bytecode to C# source code - A tool that runs .NET code in Java - all IKVM conversions are Java > .NET ## Support - .NET Framework 4.7.2 and higher (SDK-style projects) - .NET 6 and higher - Java SE 8 - Windows x86/x64/ARM/ARM64 - Linux x64/ARM/ARM64 (GLIBC and MUSL) - Mac OS X x64/arm64 Various differences exist between support for all of our different artifacts. For instance, there are some platforms we cannot distribute images for and some platforms we cannot distribute tools for. ## Installation ### NuGet ```console PM> Install-Package IKVM ``` Or, to use `MavenReference`: ```console PM> Install-Package IKVM.Maven.Sdk ``` ### Tools The tools are available for download on the [Releases](https://github.com/ikvmnet/ikvm/releases) page. ### Runtime Images Both a JRE and JDK runtime image are available. These images are standard JRE or JDK directory structures containing all of the standard tools: javac, jdeps, policytool, keytool, etc. Some Java libraries may require either a JRE or JDK, and if so, the `IKVM.Image.JRE` or `IKVM.Image.JDK` package should be added to your project. ```console PM> Install-Package IKVM.Image.JRE PM> Install-Package IKVM.Image.JDK ``` A standalone JDK distributable is available for download on the [Releases](https://github.com/ikvmnet/ikvm/releases) page. This directory structure should suffice as a `JAVA_HOME` path for standard Java applications. ## Usage IKVM supports integration with .NET SDK-style projects as well as low level tools for running compiled Java code directly or for advanced build scenarios. The 2 main entry points for integration with the .NET SDK-style projects are `IkvmReference` and `MavenReference`. .NET SDK-style projects can be built on the command line directly or using an IDE that supports them, such as recent versions [Visual Studio](https://visualstudio.microsoft.com/downloads/) or [JetBrains Rider](https://www.jetbrains.com/rider/). ### IkvmReference IKVM includes build-time support for translating Java libraries to .NET assemblies. Install the `IKVM` package in a project that requires references to Java libraries. Use `IkvmReference` within an `ItemGroup` to indicate which Java libraries your project requires. #### Example ```xml <ItemGroup> <PackageReference Include="IKVM" Version="Version" /> </ItemGroup> <ItemGroup> <IkvmReference Include="..\..\ext\helloworld\helloworld-2.0.jar" /> </ItemGroup> ``` The output assembly will be generated as part of your project's build process and a reference will automatically be added to your project so you can call APIs of the compiled `.jar` assembly. Additional metadata can be added to `IkvmReference` to customize the assembly that is generated. #### Syntax ```xml <ItemGroup> <IkvmReference Include="..\..\ext\helloworld\helloworld-2.0.jar"> <AssemblyName>MyAssembly</AssemblyName> <AssemblyVersion>3.2.1.0</AssemblyVersion> <AssemblyFileVersion>3.0.0.0</AssemblyFileVersion> <DisableAutoAssemblyName>true</DisableAutoAssemblyName> <DisableAutoAssemblyVersion>true</DisableAutoAssemblyVersion> <FallbackAssemblyName>MyAssemblyFallback</FallbackAssemblyName> <FallbackAssemblyVersion>3.1.0.0</FallbackAssemblyVersion> <KeyFile>MyKey.snk</KeyFile> <DelaySign>true</DelaySign> <Compile>SomeInternalDependency.jar;SomeOtherInternalDependency.jar</Compile> <Sources>MyClass.java;YourClass.java</Sources> <References>SomeExternalDependency.jar;SomeOtherExternalDependency.jar</References> <Aliases>MyAssemblyAlias;helloworld2_0</Aliases> <Debug>portable</Debug> </IkvmReference> </ItemGroup> ``` #### Attributes and Elements The following values can be used as either an attribute or a nested element of `<IkvmReference>`. | Attribute or Element | Description | |---|---| | `Include` (attribute only) | The identity of the `IkvmReference` item. The value can be one of: <ul><li>path to a JAR file</li><li>path to a directory</li><li>an otherwise unimportant name</li></ul> | | `AssemblyName` | By default the `AssemblyName` is generated using the rules defined by the [`Automatic-Module-Name` specification](#automatic-module-name-specification). To override this, do so here. The value should not include a file extension, `.dll` will be appended automatically. | | `AssemblyVersion` | By default the `AssemblyVersion` is generated using the rules defined by the [`Automatic-Module-Name` specification](#automatic-module-name-specification). To override this, do so here. | | `AssemblyFileVersion` | By default the `AssemblyFileVersion` is generated using the rules defined by the [`Automatic-Module-Name` specification](#automatic-module-name-specification) or, if overridden, the same value as `AssemblyVersion`. To override this, do so here. | | `DisableAutoAssemblyName` | If `true` disables detection of `AssemblyName`. | | `DisableAutoAssemblyVersion` | If `true` disables detection of `AssemblyVersion`. | | `FallbackAssemblyName` | If `AssemblyName` is not provided or cannot be calculated, use this value. | | `FallbackAssemblyVersion` | If `AssemblyVersion` is not provided or cannot be calculated, use this value. | | `KeyFile` | Specifies the filename containing the cryptographic key. When this option is used, the compiler inserts the public key from the specified file into the assembly manifest and then signs the final assembly with the private key. | | `DelaySign` | This option causes the compiler to reserve space in the output file so that a digital signature can be added later. Use `DelaySign` if you only want to place the public key in the assembly. The `DelaySign` option has no effect unless used with `KeyFile`. | | `Compile` | A semi-colon separated list of Java class path items to compile into the assembly. By default this value is the `Identity` of the item, if the identity of the item is an existing JAR file or directory (not yet supported). MSBuild globs are supported to reference multiple JAR or .class files. | | `Sources` | A semi-colon separated list of Java source files to use during documentation generation.