Introduction
Have you ever (for some reason or other) needed to use C# from within a Java program? Ever wondered how you could possibly make C# calls from within Java? Well, I will try to explain what is needed in this whole process.
Background
I was working on some Keyboard Hooking problems, and found it very easy to develop it using C#. The problem was that I was trying to develop a solution (originally) for a Java based program. After much Internet searching, I finally stumbled onto a really good article that started to put the pieces together. The article "Experience in integrating Java with C# and .NET" by Judith Bishop, R. Nigel Horspool, and Basil Worrall, was the insight I needed to start this project.
That article does show a method to use C# within a Java program; however, I didn't find it was easy to understand the whole process. After I actually had C# working within a Java program, I realized that the process could become a CodeProject article (my first article).
Using the Code
This figure is taken from the article "Experience in integrating Java with C# and .NET" by Judith Bishop, R. Nigel Horspool, and Basil Worrall.
I guess the best way to use this code is to experiment with it, and use it as a template for a project. I obviously didn't do anything terribly complicated, by just putting up a "Hello World" example, but I wanted people to see the easiest way possible first. The sample code is simply a console based Java program which will show the "Hello World, from C#" message. I'm also including all the source code and projects in all four languages.
Why the need for so many wrappers, you may ask. Well, several layers of wrapping are needed because the DLL produced by compiling a C# program into a library is not compatible with Java's JNI. The double layer of C++ above is required because the DLL with which the JNI subsystem interacts with has to be static, procedural code (not object oriented). So, the first layer is essentially C code. Fortunately, static C code will accommodate (static) pointers to C++ objects. It's doubtful whether the static C code could interact directly with a C# object, since there are things like garbage collection to consider.
Java Section
I was using Netbeans 4.0 as my main Java IDE at the time, and because of that, the process of using native code was a little more complicated. The reason for that is because a Netbeans project wants to put code inside packages rather than just use the default namespace. The javah console program, however, doesn't look at the package, and therefore doesn't correctly make the header in the right namespace. So, as I found out, there's a simple two second fix, which just requires you to edit the generated header file to correctly make the connection through JNI to the native methods in C++.
Here is the only Java code, which resides in the helloworld
package:
public class HelloWorld {
public native void displayHelloWorld();
static {
System.loadLibrary("HelloWorld");
}
public static void main (String[] args) {
new HelloWorld().displayHelloWorld();
}
}
So then, to make this into the header which is needed by the C++ library, this command needed to be run:
javah -jni helloworld.java
That step produces the following header:
#include <jni.h>
#ifndef _Included_HelloWorlds
#define _Included_HelloWorld
#ifdef _cplusplus
extern "C" {
#endif
JNIEXPORT void JNICALL
Java_HelloWorld_displayHelloWorld (JNIEnv *, jobject);
#ifdef __cplusplus
}
#endif
#endif
However, if we don't change the generated header, then the JNI call will fail as the method has a different signature due to NetBeans and the package. So the JNIEXPORT line is changed to:
JNIEXPORT void JNICALL Java_helloworld_HelloWorld_displayHelloWorld (JNIEnv *, jobject);
C++ Library
The purpose of the C++ library is to become the JNI Wrapper for the call (through the Managed C++ wrapper) to the endpoint C# code.
#include <jni.h>
#include "Java\HelloWorld.h"
#include "MCPP\HelloWorld.h"
JNIEXPORT void JNICALL
Java_helloworld_HelloWorld_displayHelloWorld(JNIEnv *jn, jobject jobj) {
HelloWorldC* t = new HelloWorldC();
t->callCSharpHelloWorld();
}
Managed C++ Library
#using <mscorlib.dll>
#using "CSharpHelloWorld.netmodule"
using namespace System;
public __gc class HelloWorldC
{
public:
CSharpHelloWorld __gc *t;
HelloWorldC() {
t = new CSharpHelloWorld();
}
void callCSharpHelloWorld() {
t->displayHelloWorld();
}
};
C# Library
The step that is required for the interaction between Managed C++ and C# is that the CSharpHelloWorld library be compiled as a .netmodule. To do this, the following command must be run from either the console or as a post-build event within the C# project (I streamlined the process by using post-build):
csc /debug /t:module "$(OutDir)\$(ProjectName).dll"
There is barely any code in this project, as I only wanted to show the simplest example possible. And what, my friends, is more simple than 'HelloWorld'?
using System;
public class CSharpHelloWorld
{
public CSharpHelloWorld() {}
public void displayHelloWorld()
{
Console.WriteLine("Hello World, from C#!");
}
}
Points of Interest
Working with Java JNI is quite a pain, especially by using Netbeans as an IDE. Hopefully, I've given you some insight as to what to expect at the different steps of this process. I must have hit every single roadblock in this project, and taken the time to look up what was needed.
History
- Version 1.0 - First release!