R.NET is an in-process bridge for the .NET Framework to access the R statistical language. R.NET works on Windows, Linux and MacOS.
On Windows, R.NET requires .NET Framework > 4.6.1 or .NET Core 2.0, and an access to the native R libraries installed with the R environment. R needs not necessarily be installed as a software on the executing machine, so long as DLL files are accessible (you may need to tweak environment variables for the latter to work, though) On Linux and MacOS, Mono is required, as well as an access to the native R libraries.
As of 2017-08
- If you want the latest binary distribution of R.NET and you are already familiar with managing dependencies with NuGet, head to R.NET on NuGet
- If you need a bit more documentation to get started, the prefered entry point is at http://rdotnet.github.io/rdotnet
Due to the move to targetting
netstandard2.0, you might encounter compiling issue if using an older toolchain. This is machine dependent (mostly, which visual studio versions and .NET targetting packs you have). You may want to adapt the instructions from the rClr packge to avoid some pitfalls.
As an example:
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\MSBuild.exeshould be the first line.
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exeis probably not a good option.
16.0.461.62831or more recent
2.1.602or more. Note that this version of the .net core SDK would prevent compilation from VS2017: VS2019 required.
If using dotnet version prior to 2.1.3, installing/restoring prerelease dependency packages is problematic. You may need to use
nuget install -Prerelease DynamicInterop -OutputDirectory packages
nuget restore RDotNet.Tests.sln dotnet build --configuration Debug --no-restore RDotNet.Tests.sln # or if any issue possibly try: # msbuild RDotNet.Tests.sln /p:Platform="Any CPU" /p:Configuration=Debug /consoleloggerparameters:ErrorsOnly
Windows, if you have several versions side by side:
set DN="C:\Program Files (x86)\dotnet\dotnet.exe" %DN% build --configuration Debug --no-restore RDotNet.Tests.sln
Unit tests can be run using:
dotnet test RDotNet.Tests/RDotNet.Tests.csproj
Normally you should get something like:
Total tests: 92. Passed: 84. Failed: 0. Skipped: 8. Test Run Successful. Test execution time: 5.2537 Seconds
However note that from time to time (or at the first
dotnet test execution) tests may fail to start, for reasons as yet unknown:
Starting test execution, please wait... The active test run was aborted. Reason: Test Run Aborted.
It may be that all subsequent calls then work as expected.
dotnet test RDotNet.FSharp.Tests/RDotNet.FSharp.Tests.fsproj
This section is primarily a reminder to the package author.
set B_CONFIG=Release :: Or for initial testing/debugging substitute Debug for Release :: set B_CONFIG=Debug %DN% build --configuration %B_CONFIG% --no-restore RDotNet.Tests.sln %DN% build R.NET/RDotNet.csproj --configuration %B_CONFIG% --no-restore %DN% build RDotNet.FSharp/RDotNet.FSharp.fsproj --configuration %B_CONFIG% --no-restore %DN% pack R.NET/RDotNet.csproj --configuration %B_CONFIG% --no-build --no-restore --output nupkgs %DN% pack RDotNet.FSharp/RDotNet.FSharp.fsproj --configuration %B_CONFIG% --no-build --no-restore --output nupkgs