Why all the extensions in the .NET Core version of JNBridgePro?

If you’ve looked at our new .NET Core components for JNBridgePro, you’ve probably noticed that there are a lot of new DLLs with names like Microsoft.Extensions.Configuration.dll. What’s up with that?

Why doesn’t the JNBridgePro for .NET Core proxy tool generate proxy DLLs?

For .NET Core-to-Java projects, you’ll need to use a proxy generation tool associated with .NET Framework. Why, and what are we going to do about this?

Differences between JNBridgePro 10.0’s support for .NET Framework and .NET Core

.NET Core and .NET Framework aren’t the same. What are the differences, and how do they affect JNBridgePro?

Why support .NET Core now?

.NET Core has been around for awhile. Why did we wait? Let’s explore our reasons.

Version 10.0 of JNBridgePro adds support for .NET Core

JNBridgePro v10 now supports NET Core. Users can now build applications that connect Java and .NET Core and run the .NET side on Windows, Linux, or – soon – MacOS.