Ugly idea/option, but you could base64 encode the R script (solely to
avoid the need to do string quoting) and have that string in the
source of the R.net code, then pass it in to the eval portion or write
it out to a temp dir and pass that to the eval portion of the code.
That way the script is embedded with the DLL and not an extra asset
that needs to be managed.
On Fri, Oct 14, 2016 at 10:43 AM, Narendra Modi <bjpmodi2...@gmail.com> wrote:
> Thanks Duncan. That's useful to know.
> On Fri, Oct 14, 2016 at 9:18 AM, Duncan Murdoch
> <murdoch.dun...@gmail.com> wrote:
>> On 14/10/2016 10:00 AM, Narendra Modi wrote:
>>> Hello Gurus,
>>> I have built a code snippet using R.net wherein I call couple of R
>>> scripts to run optimization packages and use the output in C# code.
>>> The way I call the R scripts is just by providing its location in the
>>> C# code.
>>> So, if I have to share the .dll of the complete program, I will also
>>> have to share the R scripts; actual code. Is there anyway to avoid it;
>>> not having to share the r script code with users/testers.
>>> I am considerably new to R. Any suggestion in this direction is
>> I don't know what the R.net .dll is, but if it includes R, you need to share
>> the complete source code of anything you distribute that includes it. The R
>> scripts will be only a small part of that.
>> Sharing less than that is a copyright violation, since you are only licensed
>> to distribute R under the GPL license, and it requires that you share code
>> of the original and your modifications.
>> Duncan Murdoch
> Remail@example.com mailing list -- To UNSUBSCRIBE and more, see
> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.
Rfirstname.lastname@example.org mailing list -- To UNSUBSCRIBE and more, see
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.