XML Configuration file

You are browsing legacy Javonet 1.5 (Java<>.NET bridge for Windows) documentation. Use the left side menu or click here to switch to latest Javonet 2.0 documentation. Javonet 2.0 allows you to use any module from JVM, CLR, Netcore, Python, Ruby, Perl, NodeJS on Windows, Linux and MacOs from any application created in Java, Clojure, Groovy, Kotlin, C#, F#, J#, VB.NET, Python, Perl, Ruby, JavaScript, TypeScript, C++ and GoLang

There are many benefits to activating and setting up Javonet using an XML configuration file. It simplifies distribution of your application to your team, lets you update the Javonet license, references and framework configuration more quickly, and avoids hardcoded activation and configuration details.

During the first application use, Javonet searches for, and then automatically uses the XML configuration file to activate and configure your application.

Simply name the file "javonet.xml" and place it in the root directory of your Java application.

Below you can find the full structure of the XML configuration file. Some of the tags are optional.

<?xml version="1.0" encoding="ISO-8859-1" ?>
<references> <!-- optional -->
<activation> <!-- mandatory -->
    <proxy> <!-- optional -->
<settings> <!-- optional (default .NET v35 and MTA) -->
    <apartmentState>STA</apartmentState> <!-- optional (default MTA) -->
    <framework>v40</framework> <!-- optional (default .NET v35) -->