If you've ever wired Java and .NET together in production, you know the runtime version treadmill never stops. Microsoft ships .NET annually, Java's on a six-month cadence, and your integration layer needs to keep up or become the bottleneck.
JNBridgePro v12.1 just dropped, and it's the first release to fully support .NET 10 alongside JDK 25 — plus something genuinely clever: a demo folder designed for AI coding assistants.
Here's what's actually in the box.
.NET 8, 9, and 10 — All Supported
v12.1 generates proxies that work natively across .NET 8 (current LTS), .NET 9, and .NET 10 — on both Windows and 64-bit Linux. No conditional compilation, no separate builds per target framework.
This matters because if you're bridging Java libraries into a .NET app, you don't want your integration tooling to be the reason you can't upgrade runtimes. With v12.1, you upgrade .NET, regenerate proxies, done.
JDK 8 Through 25 + Jakarta EE 11
On the Java side, full coverage from JDK 8 all the way to JDK 25, plus Java EE 8 through Jakarta EE 11. That's the entire range from legacy Java 8 monoliths to brand-new Jakarta EE deployments — no version gaps.
If you're maintaining a Java 8 app that talks to a .NET 10 service (or vice versa), this is the kind of compatibility range that means you don't have to synchronize your upgrade schedules across stacks.
AI-Assisted Configuration — The Demo Folder
This is the clever addition. v12.1 ships with a demo folder containing a README and all the configuration files in the correct places. Hand that folder to Claude Code, Copilot, or any AI coding agent with file access, and it instantly knows how to configure JNBridgePro for your system. You can also paste the README into ChatGPT for guidance.
The idea is dead simple: instead of reading through setup docs, you give your AI coding assistant the demo folder and go from zero to configured in minutes. The folder covers:
- Proxy generation configs — correctly structured so an AI agent can adapt them to your Java classes and .NET targets
- TCP/binary and shared memory communication — reference patterns an AI can scaffold your transport layer from
- Deployment patterns — common enterprise scenarios ready for an AI assistant to adapt to your environment
Configuration is where most integration time gets burned, not the actual coding. Having a folder that an AI assistant can immediately parse and work from cuts that setup time dramatically.
What JNBridgePro Actually Does (Quick Refresher)
For those who haven't used it: JNBridgePro generates proxy classes that let you call Java from C# (or C# from Java) using native syntax. No REST wrappers, no message queues, no serialization layers — direct in-process or TCP-based method calls.
You point it at Java classes, it generates .NET proxies. You call those proxies like regular C# objects. Under the hood, it handles marshaling, type conversion, and communication. It's been the go-to for enterprise Java/.NET integration for 20+ years.
Who Should Care
- Teams running mixed Java/.NET stacks who need to stay current on both runtimes
- Anyone on .NET 9/10 who needs Java library access without downgrading
- Shops using AI coding assistants — hand the demo folder to Claude Code or Copilot and go from zero to configured
- Legacy Java 8 maintainers bridging into modern .NET — full compatibility, no workarounds
Try It
Download JNBridgePro v12.1 — free evaluation, no credit card.
What's your team's Java/.NET integration setup look like? Still hand-rolling REST wrappers, or using something more direct? Curious what approaches people are running in production.
Top comments (0)