Closed halcwb closed 2 years ago
In both logs findRHomePath: file='C:\Program Files\R\R-3.5.3\bin\x64\R.dll'
. That would be an issue if mixed with 3.4.3. RProvider is using R.NET 1.6.5 which cannot work with R 3.5 in any case. There is a pre-release https://www.nuget.org/packages/R.NET/1.8.0-alpha1 that should let a future RProvider work with R 3.5.
In the meantime, there should be ways to define the environment variable R_HOME set e.g. to 'C:\Program Files\R\R-3.4.3' to make sure that version is loaded. I may overlook the exact procedure though; will try to take a look after work.
I removed R 3.5, so only 3.4.3 is installed. So, the in the last log, the last attempt records:
findRHomePath: file='C:\Program Files\R\R-3.4.3\bin\x64\R.dll'
Still no luck, I also applied solution: https://github.com/jmp75/rdotnet/issues/62#issuecomment-369065108.
It would be nice if the creators of FsLabs would weigh in.
I cannot get it to work with R 3.4.3. But R 3.4.2 works. Here's my setup.
C:\R\R-3.4.2
R_HOME = C:\R\R-3.4.2\
We are no longer supporting the use of the FsLab nuget package - it is no longer under active development. Support for newer R versions than 3.4.2 has now been added to RProvider standalone. If the issue re-occurs with the standalone upcoming RProvider 2 release on .net 5, please re-open this issue. Thanks!
Trying to use RProvider out of the box via the FsLabs template runs into an exception using the RDotNet library, see attached file. rprov_log.txt
Also tried it by downgrading R to 3.4.3 see additional attachment rprov_log.txt