MASES.JCOReflectorCLI 1.8.5

There is a newer version of this package available.
See the version list below for details.
dotnet tool install --global MASES.JCOReflectorCLI --version 1.8.5
This package contains a .NET tool you can call from the shell/command line.
dotnet new tool-manifest # if you are setting up this repo
dotnet tool install --local MASES.JCOReflectorCLI --version 1.8.5
This package contains a .NET tool you can call from the shell/command line.
#tool dotnet:?package=MASES.JCOReflectorCLI&version=1.8.5
nuke :add-package MASES.JCOReflectorCLI --version 1.8.5

JCOReflector (a .NET Java wrapper)


.NET Framework .NET 5 .NET 6
Maven Central Maven Central Maven Central
JCOReflectorEngine JCOReflectorCLI
latest version downloads latest version downloads

The project

JCOReflectorEngine produces a set of .NET wrapper for Java as JARs that are available for download. It's simple to use: you only need to reference JCOReflector.jar in the class-path and use the .NET API within your Java projects like exposed in the example section.

The core of the project is the innovative JCOReflector, a reflection engine which automatically writes Java classes using .NET class reflection. JCOReflector can be used to reflects any .NET assembly (even assembly outside the Microsoft ones) into JARs. The generated wrapper classes are based on the powerful JCOBridge engine and extends its use to simplify the use of .NET from Java(JVM). It was created internally from us to support our customers, now we made it available for everyone.

This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to

Runtime engine

JCOReflector uses JCOBridge, and its features, to obtain many benefits:

  • Cyber-security:
    • JVM and CLR, or CoreCLR, runs in the same process, but are insulated from each other;
    • JCOBridge does not make any code injection into CLR or JVM;
    • JCOBridge does not use any other communication mechanism than JNI;
    • JVM inherently inherits the cyber-security levels of running .NET (CLR);
  • Direct access the CLR from any JVM application:
    • No need to learn new APIs: we try to expose the same .NET APIs in Java style;
    • No extra validation cycle: bug fix, improvements, new features are immediately available;
    • Documentation is shared;

Have a look at the following resources:

History of the project

This project started in 2019 with the aims to create a set of Java (JVM) classes which mimic .NET (Framework/Core) conterparts, in May 2020 the first commit in GitHub. Using this project it is possible to use .NET API in Java and all JVM enabled languages (Scala, Kotlin, and so on). The final output of JCOReflector are JARs. At its first stages no JARs was available: only the JCOBridge engine, the graphical UI that helps to manages reflection and the operations needed to finally build JARs was relased. Starting from recent relases automated continous integration and verification process are in places, so the produced JARs are directly available for download and is no more needed to manually rebuils JARs before use it. Anyway still possible to use JCOReflector to reflects any .NET assembly (even assembly outside the Microsoft ones) into JARs, and because JCOReflector uses templates it is not necessary to manually manages the output, special needs can be addressed dirctly inside the templates.

Simple example

package mscorlib;

import system.*;

public class HelloNET {
    public static void main(String[] args) {
        try {
            String filename = "test.txt";
            String result = "";
            if (File.Exists(filename)) {
                result = File.ReadAllText(filename);
                result = result + "Java Execution ";
                File.WriteAllText(filename, result);
        } catch (FileNotFoundException fnfe) {
        } catch (Throwable tre) {

This is the result:

prompt> This is a text file for read/write operation
prompt> This is a text file for read/write operation Java Execution
prompt> Exiting

To run it runs a command like the following one:

java -cp JCOReflector.jar;. HelloNET

The full example code, and other ones, are in the project test folder.

A basic Scala examples is the following one:

package mscorlib

import system.Console
import system.Environment

object HelloIterator {
  def main(args: scala.Array[String]): Unit = {
    try {
    } catch {
      case tre: Throwable =>

the same example written in Kotlin is the following one:

package mscorlib

import system.Console
import system.Environment

object HelloIterator {
    fun main(args: Array<String>) {
        try {
            for (drive in Environment.GetLogicalDrives()) {
        } catch (tre: Throwable) {

Whats in .NET for Java?

From the point of view of .NET it is very simple to use Java classes and it is not necessary to have some kind of reflection classes. JCOBridge is able to access and execute directly within a JVM using C# code, from C# it is possible to execute directly Java code with a similar syntax: look at the examples in JCOBridge-Examples

Actual state

The JCOBridge is a mature platform for .NET assembly reflection, the .NET wrapper JARs are available and cover most of the .NET framework functionality.
The reflector executables, available for both Framework and CoreCLR, is limited in the following features:

Implemented in the reflector

Not implemented in reflector:

  • Out/Ref parameters: you need to write code using JCOBridge API
  • Generic types
  • Method decoration (Attributes)
  • Unsafe methods
  • Fields


C# and Java are different languages. The reflection process cannot reflects into Java some features available on C#: an example are properties where get/set is automatically choosed from C# compiler Other limitations comes from some differences between the two engines (CLR and JVM). In all cases JCOBridge superside these limitations, but manual operations shall be made: do not change the reflected classes, override them in your code.

How to use the generator tool (JCOReflector)

In the root folder execute:

dotnet build JCOReflector\JCOReflector.sln


dotnet build JCOReflector\JCOReflectorCLI.sln

Within the folder bin you will find three subfolders:

  • net461 (available only on Windows platform)
  • netcoreapp3.1 (available on .NET Core supported platforms)
  • net5.0 (available on .NET 5 supported platforms)
  • net6.0 (available on .NET 6 supported platforms)

in each subfolder will be available two executables:

  • JCOReflectorCLI the CLI tool;
  • JCOReflectorGUI the GUI tool, below some screenshot:

JCOReflector JCOReflector

Reflected Assemblies

The folder netreflected contains all reflected classes generated for .NET Framework (net461), Core (netcoreapp3.1), 5 (net5.0) and 6 (net6.0). Below the coverage statistics and the list of analyzed and reflected assemblies:










Product Compatible and additional computed target framework versions.
.NET net5.0 is compatible.  net5.0-windows was computed.  net6.0 is compatible.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp3.1 is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

Version Downloads Last updated
1.14.0 72 5/19/2024
1.13.1 187 1/23/2024
1.13.0 227 11/26/2023
1.12.1 303 2/26/2023
1.12.0 285 2/8/2023
1.11.0 428 8/18/2022
1.10.1 422 4/6/2022
1.10.0 432 3/30/2022
1.9.3 421 3/15/2022
1.9.2 416 3/14/2022
1.9.1 425 3/11/2022
1.9.0 432 3/10/2022
1.8.6 451 3/4/2022
1.8.5 448 3/2/2022
1.8.4 450 2/25/2022
1.8.3 424 2/7/2022
1.8.2 272 12/31/2021
1.8.1 446 11/22/2021
1.8.0 304 11/15/2021
1.7.3 351 10/19/2021
1.7.1 299 10/11/2021
1.7.0 288 9/1/2021