Version 10.0 of JNBridgePro adds support for .NET Core




The tenth major release of any product is a big deal, and JNBridgePro 10.0 is no exception. This version adds one of the biggest new features ever: support for a new platform — .NET Core 3.0. Users can now build and run applications that connect Java and .NET where the .NET side can be on Windows, Linux, or – soon – MacOS.

We still fully support the regular .NET Framework. In fact, .NET Framework is still a bit more feature rich, so there are several features that we support for .NET Framework but not yet for .NET Core.

Why now, as .NET Core has been available for a while? Early releases of .NET Core lacked some crucial APIs that we needed for JNBridgePro, so we were forced to wait. Even as those APIs became available, .NET Core was a moving target, and the offered APIs appeared to lack commercial stability. .NET Core 3.0 feels like an inflection point. The new version seems fairly stable and complete, and Microsoft has even issued guidance that new .NET projects should be implemented on .NET Core 3.0 unless there’s compelling reason to do otherwise. As of this writing .NET Core 3.0 is still in preview, but appears solid. We’ll be tracking it as new versions are released, and will make adjustments if anything breaks. You should be confident that things will work when .NET 3.0 goes into general availability. We’ll have more to say about why we chose to develop for .NET Core 3.0 in a future blog post.

We will be presenting a series of blog posts on the new .NET Core capability over the next few weeks, including the aforementioned discussion of our choice of .NET Core 3.0, the differences in how our product works with .NET Framework and .NET Core, and a set of examples of how to use JNBridgePro with .NET Core on both Windows and Linux.

In addition to support for .NET Core 3.0, JNBridgePro 10.0 also includes plug-in support for Visual Studio 2019, and includes a new whitelist feature for enhanced security when creating .NET-to-Java projects that use TCP/binary and HTTP/SOAP communications. We’ll have more about that in a future blog post, too.

See more about our support for .NET Core.

As always, do let us know if you have any questions, comments, or suggestions for new features.