The old .NET implementation was based on the open source project IKVM, which is no longer under development. For this reason we have implemented this new .NET bridge API. Since the old IKVM-based solution will be removed in one of the next major versions, we recommend to use this new bridge API when starting a new project.
The bridge API starts a Java process running the product in the background. It will then operate as a bridge to this process.
The bridge API is able to run on any OS with .NET runtime and Java runtime installed. There is no limit to a 32 bit or 64 bit architecture. The .NET and the Java process don't need to use the same architecture.
<project folder>\ # the root of your Visual Studio project <any folder>\ # the location of this folder is not important, it must be a sub folder of the project or the root inetsoftware.Reporting.dll # the reference must be added to the Visual Studio project plugins\ processbridge.zip # base process bridge API processbridge.reporting.zip # reporting specific bridge API *.zip # any further feature you want to use core\ inetcore.jar # basic platform API ClearReports.jar # basic reporting API *.jar # more optional features lib\ **/*.jar # optional jar files like drivers and beans runtime\ # optional Java runtime, if not available the Java VM of the system is used bin\ java.exe # it looks for this file to find the optional Java runtime *.* # all Java VM files
If you want to test this API with Visual Studio or Rider then:
If you're running any of the provided powershell script you might need to prepare your environment. Powershell scripts are disabled by default. Here is what you need to do:
# activate powershell scripting temporarily powershell.exe -ExecutionPolicy Unrestricted # go into previously created folder (please modify accordingly) cd <project folder>\<any folder> # execute script & '<sdk>\Documentation and Samples\dotnet - Samples\PowerShell\RenderPdfFile.ps1'