This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • Ignite.NET Development
Skip to end of metadata
Go to start of metadata


Ignite.NET is built on top of Ignite and provides native APIs for .NET developers.


For Linux instructions see below.

  • Oracle JDK 7+
  • .NET Framework 4.0+
  • PowerShell 3.0+
  • Visual Studio 2010+
  • Apache Maven

Getting Started With Modern Tooling

Even though Ignite.NET can be developed and run on VS2010 and JDK7, it is more common to use latest Visual Studio and JDK.

Assuming that we are on up-to-date Windows x64 installation:

Install software

  1. Install Java JDK (not JRE) 8.x (Java 9 is not supported):
  2. Set JAVA_HOME environment variable to point to the JDK installation directory (something like "C:\Program Files\Java\jdk1.8.0_111")
  3. Download and unzip Apache Maven to some folder:
  4. Add Maven bin folder to PATH environment variable (example: "c:\Programs\Maven\apache-maven-3.3.9\bin\")
  5. Install Visual Studio 2017 (free Community Edition will do).

Get source code

For more details on working with GitHub forks and pull requests see How to Contribute#GitProcess

Build Java sources

In root source folder execute "mvn clean package -DskipTests -Dmaven.javadoc.skip=true -U -Plgpl,-examples,-clean-libs,-release,-scala,-clientDocs" command.

When doing pure .NET development, you only need to run this every time you update your branch from master.

Build .NET sources

  • Open modules\platforms\dotnet\Apache.Ignite.sln in Visual Studio
  • Build solution

Running Unit Tests

Ignite.NET uses NUnit for unit tests. You can run them with ReSharper right away, or with NUnit Test Adapter for Visual Studio.

  • Make sure to disable assembly shadow copy in unit test runner settings

Running Tests On TeamCity

  • Ignite uses TeamCity-based continuous integration:
  • If you do .NET-only development, you are interested only in test suites having "Platform.NET" in the name
  • Create an account to be able to start new runs
  • .NET NuGet suite can be used to produce release NuGet binaries (see Artifacts tab of a finished build)

Coding Guidelines

Coding guidelines compliance is checked by .NET Inspections TeamCity suite (see below).

Static Code Analysis

Three code analysis tools are integrated with Ignite.NET project:

All these tools assume that project has been built in Debug Any CPU mode.

Building Release Binaries

There is a build.ps1 file in modules/platforms/dotnet folder (and build.bat that just calls build.ps1 so you don't have to run PowerShell manually).

This build script performs end to end build, including Java, .NET and NuGet.

To build everything and produce release binaries (in bin folder) and NuGet packages (in nupkg folder), run the script without parameters.

Run `Get-Help .\build.ps1 -detailed` PowerShell command to view detailed build script documentation.

Getting Started on Linux and macOS

Ignite.NET can be built, developed, and tested on Linux and macOS, but only partially.
A subset of functionality and tests is available. See Apache.Ignite.DotNetCore.sln.


  • JDK: sudo apt-get install default-jdk
  • Maven: sudo apt-get install maven
  • IDE: Not required. Rider is recommended.

Getting started

    • Build Java and .NET: ./

    • Run tests: cd Apache.Ignite.Core.Tests.DotNetCore & dotnet test

    • Run specific test: dotnet test --filter CacheTest

    • IDE: Open Apache.Ignite.DotNetCore.sln
  • No labels