Nov 13, 2014 at 1:09 PM
Edited Nov 13, 2014 at 1:54 PM
Hi, thanks for your prompt reply.
I moved to trying to specify the file-path explicitly ... only as a "last resort" ... because
the expected behavior after the package install via Nuget
: that one could invoke REngine.SetEnvironmentVariables(); with no argument does not work.
Note that I read "issue 128" before I installed R: in fact, a comment there was useful in deciding which of the two choices for R.NET in Visual Studio Gallery to install.
I've examined the source of R's 'CreateInstance method: I notice a use of "R.dll" : you also mentioned that: on this machine there is no R.dll.
Setting the filepath used as an argument to 'SetEnvironmentVariables to the _directories ... not the .dll ... that contain the RDotNet.dll does not work: the same missing Registry Key error is thrown reported in my first post.
On my system the RDotNet.dll and other dll's are in two places:
- in the project folder path shown in my original post
- in a temp folder created by NuGet:
C:\Users... redacted ...\AppData\Local\Temp\nuget\R.NET.Community.1.5.16\lib\net40