Ritch Melton

Here's an initial callstack for the exception causing the crash. This is a debug build, but my symbol paths are dorked up, so there isn't any file info.  For...

@manjotsingh20 This is the very common R.Net Library load issue when running from IIS. Please follow the instructions in this issue (https://rdotnet.codeplex.com/workitem/117).

Did you try the sample mentioned in that work item, ie: `print(summary((1:5))`? Does that work? If that doesn't work for you, I don't know what to tell you without some...

I'd love to see your work. I was never really thrilled with the CStackLimit hack, but it doesn't seem to cause real problems.

I agree with the concept for thread safety, but one of my issues with the way the R API is imported is that I believe there should be a C#...

Its really just a shim, a minor extra level of indirection that consolidates R code and platform specific identities in one place. The current implementation is written with WCF and...

Wow. Talk about unintended consequences. Are you ok with reverting to an older version in nuget for now?

I'll give it a try today

I'm not seeing a difference between R.Net and rstudio. If I run this code in RStudio ``` library(track); track.start(clobber = "vars", dir = file.path(tempdir(), 'rdata12356')) a

Have you tried using source in R.Net as suggested in that SO link? RStudio and R.Net use the publicly documented API for invoking the R engine, so what works in...