Ignite.NET is built on top of Ignite and provides native APIs for .NET developers.
For Linux instructions see below.
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:
For more details on working with GitHub forks and pull requests see How to Contribute#GitProcess
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.
Coding guidelines compliance is checked by .NET Inspections TeamCity suite (see below).
Three code analysis tools are integrated with Ignite.NET project:
All these tools assume that project has been built in Debug Any CPU mode.
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.
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.
Build Java and .NET: ./build.sh
Run tests: cd Apache.Ignite.Core.Tests.DotNetCore & dotnet test
Run specific test: dotnet test --filter CacheTest